Cardinal MCP ServerYour AI assistant, fluent in Cardinal

A Model Context Protocol server that connects AI assistants such as Claude, Codex, Cursor or GitHub Copilot to the Cardinal SDK. Your assistant can search the documentation and, once you log in, call the SDK against your Cardinal backend on your behalf.

View on npmRead the documentation

Search the documentation

APIs, models, filters, tutorials and how-to guides, matching the SDK version of the server. No account needed.

Operate the SDK

After you log in, the assistant can call the TypeScript SDK for you: manage users, roles and groups, work with patients, healthcare parties and devices, inspect keys.

How to use it

Two ways to connect your assistant, depending on what you need.

Option 1

Fully local

The server runs on your own machine, started by your AI assistant through npx. This is the complete experience: documentation and SDK operations.

  • Documentation search and SDK operations
  • Encryption keys are stored on your machine only
  • Requires Node.js, npx comes with it
Claude Code
claude mcp add cardinal -- npx -y @icure/cardinal-mcp-server
Claude Desktop and other clients
{
  "mcpServers": {
    "cardinal": {
      "command": "npx",
      "args": ["-y", "@icure/cardinal-mcp-server"]
    }
  }
}
Codex, Cursor, VS Code and version pinning are covered in the documentation
Option 2Coming soon

Hosted by iCure

Connect your assistant to a server that we host. There is nothing to install, and it provides documentation and instructions only.

  • Documentation search and guidance on how to use the SDK
  • Nothing to install or to keep up to date
  • No operations on your data

Why instructions only?

Reading or writing Cardinal data requires your encryption keys, and by design we cannot host them. To let your assistant work on your data, use the fully local option.

Use it safely

Everything you type reaches the AI model, and the assistant acts with the rights of the user you log in with. Use a test group or a dedicated user with the least privileges that get the job done, never a production administrator. Keep the key storage directory outside your repository and do not commit it.

View on npmRead the documentation