cheqd MCP Server

What does “cheqd” MCP Server do?

The cheqd MCP (Model Context Protocol) Server serves as a toolkit for cheqd decentralized identity. As an MCP server, it is designed to connect AI assistants with decentralized identity systems and related external data sources or services. This enables enhanced AI-driven workflows in digital identity management, such as secure identity verification, credential management, and integration with decentralized networks. By providing standardized interfaces, the cheqd MCP Server facilitates tasks like querying identity data, managing digital credentials, and interacting with APIs, thereby improving developer efficiency when building identity-focused AI applications.

List of Prompts

No prompt templates are mentioned in the repository.

Ready to grow your business?

Start your free trial today and see results within days.

Request demo Log in

List of Resources

No explicit MCP resources are described in the repository.

List of Tools

No specific tools are listed in server.py or equivalent files in the repository.

Join our newsletter

Get latest tips, trends, and deals for free.

Email address

Subscribe

Use Cases of this MCP Server

• Decentralized Identity Management
  Integrate with cheqd’s decentralized identity platform to create, manage, and verify digital identities programmatically through AI assistants.
• Credential Issuance and Verification
  Automate the process of issuing and verifying digital credentials, streamlining workflows for organizations that require trusted digital verification.
• Interoperability with Decentralized Networks
  Enable AI agents to interact with different decentralized identity solutions, fostering cross-platform compatibility and data exchange.
• Enhanced Security Workflows
  Leverage decentralized identity features for secure authentication and authorization in AI-driven applications.
• Compliance and Regulatory Automation
  Simplify identity compliance processes by allowing AI agents to query and validate identity data against regulatory requirements.

How to set it up

Windsurf

1. Ensure you have Node.js installed.
2. Locate your Windsurf configuration file.
3. Add the cheqd MCP Server as a new MCP server using a JSON snippet.
4. Save the configuration and restart Windsurf.
5. Verify the server is running and accessible.

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"]
    }
  }
}

Securing API keys:

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"],
      "env": {
        "CHEQD_API_KEY": "${CHEQD_API_KEY}"
      },
      "inputs": {
        "apiKey": "${CHEQD_API_KEY}"
      }
    }
  }
}

Claude

1. Ensure you have Node.js installed.
2. Open your Claude configuration file.
3. Add the cheqd MCP Server configuration in the mcpServers section.
4. Save and restart Claude.
5. Confirm the MCP server is active.

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"]
    }
  }
}

Securing API keys:

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"],
      "env": {
        "CHEQD_API_KEY": "${CHEQD_API_KEY}"
      },
      "inputs": {
        "apiKey": "${CHEQD_API_KEY}"
      }
    }
  }
}

Cursor

1. Make sure Node.js is installed.
2. Edit the Cursor configuration file.
3. Insert the cheqd MCP Server configuration in the mcpServers object.
4. Save changes and restart Cursor.
5. Check that the MCP server is registered.

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"]
    }
  }
}

Securing API keys:

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"],
      "env": {
        "CHEQD_API_KEY": "${CHEQD_API_KEY}"
      },
      "inputs": {
        "apiKey": "${CHEQD_API_KEY}"
      }
    }
  }
}

Cline

1. Confirm Node.js is installed.
2. Access your Cline configuration file.
3. Add the cheqd MCP Server entry to the mcpServers object.
4. Save and restart Cline.
5. Verify that the MCP server is functioning.

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"]
    }
  }
}

Securing API keys:

{
  "mcpServers": {
    "cheqd-mcp": {
      "command": "npx",
      "args": ["@cheqd/mcp-server@latest"],
      "env": {
        "CHEQD_API_KEY": "${CHEQD_API_KEY}"
      },
      "inputs": {
        "apiKey": "${CHEQD_API_KEY}"
      }
    }
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "cheqd-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “cheqd-mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Our opinion

Based on the information available in the repository, the cheqd MCP Toolkit offers a foundation for decentralized identity integration but lacks clear documentation on MCP-specific features like prompts, resources, and tools. The presence of a license is positive, but its utility for AI workflows needs further development. Overall, the repository rates a 3 out of 10 as an MCP server due to missing core MCP documentation and feature exposure.

MCP Score