KeyID MCP for Claude and Cursor

Complete registration flows in Claude or Cursor.

KeyID exposes a hosted MCP endpoint at https://keyid.ai/mcp for Claude and Cursor connectors, plus a local stdio package when you want bring-your-own keys and the same registration session model.

47 workflow tools 8 prompts 7 resources Registration sessions + browser continuity

Install options

Use the hosted endpoint first. Keep the local stdio package for developer-controlled identity and offline-style workflows.

Remote OAuth

Hosted remote endpoint

https://keyid.ai/mcp

Local BYO keypair

Local stdio package

{
  "mcpServers": {
    "keyid": {
      "command": "npx",
      "args": ["-y", "@keyid/agent-kit"]
    }
  }
}

Developer fallback

Claude Code CLI

claude mcp add keyid -- npx -y @keyid/agent-kit

Identity behavior

Hosted mode creates a managed KeyID install identity for the connector and stores the private key encrypted at rest, so signup sessions and browser continuity survive across chat sessions.

The core workflow is session-based: start one signup session per service, wait for the right artifact, save browser state, and close the session explicitly as completed or blocked.

Local mode keeps identity under your control. Reuse the same Ed25519 keypair across machines by setting KEYID_PUBLIC_KEY and KEYID_PRIVATE_KEY.

Copy-paste prompts

These prompts are written for chat-first workflows where the model should stay inside the KeyID MCP surface as long as possible.

Provision a KeyID identity and start a signup session for Stripe with email artifacts only.
Wait for the next artifact on that signup session and return the best action to take in the browser.
Save the current browser cookies and localStorage for this session after the account reaches the billing screen.
If the site blocks progress, mark the session blocked and explain whether it was CAPTCHA, rate limiting, or a missing message.
Show recent signup sessions and the latest TOTP services for this identity.

Expected tool sequence

`provision_identity` — Create or reveal the email identity for this MCP session.
`start_registration_session` — Start a signup session that correlates email, SMS, or TOTP artifacts for one service.
`wait_for_registration_artifact` — Poll a signup session until an artifact arrives or the session expires, blocks, or times out.
`get_registration_artifacts` — Fetch the normalized artifacts attached to a signup session in priority order.
`save_browser_state` — Store cookies and browser session state for a signup session in the KeyID vault.
`save_registration` — Create or update a registration record for an external service.
`complete_registration_session` — Mark a signup session complete after the browser flow succeeds.

Failure and recovery notes

If the connector asks to authorize again, complete the OAuth flow and retry the MCP call.
If local mode keeps generating a new identity, provide KEYID_PUBLIC_KEY and KEYID_PRIVATE_KEY explicitly.
If a signup session never receives an artifact, tighten expectedSenders or expectedArtifactTypes before creating another session.