Claude

Run KeyID inside Claude with hosted or local MCP.

Use the hosted OAuth connector when you want zero setup, or run the local stdio package when you want your own Ed25519 keypair and portable identity for the same registration-session workflow.

Remote Endpoint Download MCPB Bundle Registration sessions
Claude Desktop Claude Code Remote OAuth connector Registration-session workflows

Install options

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

Local stdio

Claude Desktop local config

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

Local stdio

Claude Code

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

Remote OAuth

Hosted remote endpoint

https://keyid.ai/mcp

One-click MCPB

Claude Desktop bundle

https://keyid.ai/downloads/keyid.mcpb

Identity behavior

Local Claude installs either reuse your supplied keypair or generate one for the machine. That identity remains stable only if you persist the keypair yourself.

Hosted Claude installs create one managed KeyID install per connector authorization. You can export or revoke that install later from the MCP install endpoints.

Claude signup workflows work best when prompts are explicit about the service, expected sender, and when browser state should be saved back to KeyID.

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 KeyID and start a signup session for GitHub before I open the browser.
  • Wait for the GitHub session artifact and stop as soon as you have a usable link or code.
  • Request a phone number only if the site requires SMS verification, then save browser state after the SMS step is passed.
  • If the flow is blocked, mark the session blocked with a reason instead of starting over.
  • Save this account registration under serviceName GitHub after the signup session is completed.

Expected tool sequence

  1. `provision_identity` — Create or reveal the email identity for this MCP session.
  2. `start_registration_session` — Start a signup session that correlates email, SMS, or TOTP artifacts for one service.
  3. `request_phone_number` — Assign a phone number to the current KeyID identity.
  4. `wait_for_registration_artifact` — Poll a signup session until an artifact arrives or the session expires, blocks, or times out.
  5. `save_browser_state` — Store cookies and browser session state for a signup session in the KeyID vault.
  6. `complete_registration_session` — Mark a signup session complete after the browser flow succeeds.
  7. `save_registration` — Create or update a registration record for an external service.

Failure and recovery notes

  • If Claude Desktop cannot start the server, confirm Node 20+ and that npx is available on PATH.
  • If remote Claude opens the docs page instead of authenticating, paste the exact MCP URL https://keyid.ai/mcp rather than the docs URL.
  • If the browser loses progress between steps, load the saved browser state for the same session before retrying the page.