AI Assistants (MCP)

SignCare runs an MCP server at mcp.signcare.io. MCP (Model Context Protocol) is an open standard that lets AI assistants call tools. Once you connect your assistant, it can:

• answer questions from the SignCare docs, with a link to the exact page and section;
• check a request body against the real API rules before you send it;
• write integration code (cURL, JavaScript, Python, PHP) and webhook receivers;
• explain an error from its status and response body, and say whether to retry;
• plan a multi-step flow, such as full digital KYC or eSign with eStamp.

Sign in#

The first time you connect, your assistant opens a browser window:

• Any SignCare account works: the same login you use for the SignCare Console. No API key, and no special access is needed.
• You stay signed in for a day. After that, your assistant asks you to sign in again.
• Signing in only lets the assistant read the SignCare docs. It can't see your password, see or change your account or data, call the SignCare API, or use your credits.
• Only continue on the SignCare page if you just asked your assistant to connect to SignCare.

Connect your assistant#

Claude Code#

claude mcp add --transport http signcare https://mcp.signcare.io/mcp

Add --scope user to use it in every project. Then start a new session and run /mcp. The first time, signcare shows as needing authentication: select it, choose Authenticate and sign in. It should then be listed as connected, with 11 tools.

Claude (web and desktop app)#

Custom connectors depend on your Claude plan, and on a Team or Enterprise plan your admin may need to allow them.

Cursor#

Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "signcare": {
      "url": "https://mcp.signcare.io/mcp"
    }
  }
}

VS Code (GitHub Copilot agent mode)#

Add this to .vscode/mcp.json, or run MCP: Add Server from the Command Palette and choose HTTP:

{
  "servers": {
    "signcare": {
      "type": "http",
      "url": "https://mcp.signcare.io/mcp"
    }
  }
}

Then open Copilot Chat in Agent mode and check that the SignCare tools are enabled.

Windsurf#

Add this to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "signcare": {
      "serverUrl": "https://mcp.signcare.io/mcp"
    }
  }
}

Other clients#

Any client that supports MCP over Streamable HTTP can use https://mcp.signcare.io/mcp. A client that only starts local (stdio) servers can connect through the mcp-remote bridge (needs Node.js):

{
  "mcpServers": {
    "signcare": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.signcare.io/mcp"]
    }
  }
}

Cursor, VS Code, Windsurf and mcp-remote open the same sign-in window the first time they connect.

To try the tools by hand, run npx @modelcontextprotocol/inspector, choose Streamable HTTP, enter the URL and sign in when asked.

What to ask#

Ask in plain words. The assistant picks the tools itself.

Some clients also show the server's ready-made prompts as slash commands: integrate-kyc, debug-signcare-error and plan-kyc-flow.

Tools#

All tools are read-only.

What it covers#

The server covers every SignCare API product: 148 endpoints in 17 product areas.

It also includes the guides on this site and 26 ready-made flows, such as full digital KYC, an eSign request tracked to completion, eStamp and sign, and company due diligence.

If something isn't covered, the assistant says so and links to the right page on this site.

How it works#

The server answers only from the SignCare documentation and API reference it was built from. Generated code calls the SignCare API from your application, with your keys, which it reads from environment variables. The MCP server itself never calls the SignCare API.

Privacy and security#

• Never paste API keys, webhook secrets or real customer data into an AI conversation. The tools use placeholders such as YOUR_API_KEY, and they warn you when something looks like a real key or Aadhaar number.
• The server does not store what you send it and does not log tool arguments.
• Generated code reads credentials from environment variables, and targets Stage (uat-ext.signcare.io) by default. Test there before you switch to Live; see Environments.
• Treat generated code like any code from a colleague: review it before it goes to production.

Troubleshooting#

Still stuck? See Support.