Cursor

Install KeyID in Cursor with one local or remote config.

Cursor supports direct MCP install deeplinks. Use the hosted endpoint for fast setup or the local package when you want the keypair on your machine and the same registration-session workflow.

Install Remote In Cursor Install Local In Cursor Registration sessions
Cursor deeplinks Hosted remote MCP Local stdio Registration-session workflows

Install options

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

Remote OAuth

Cursor remote config

{
  "mcpServers": {
    "keyid": {
      "url": "https://keyid.ai/mcp"
    }
  }
}

Local stdio

Cursor local config

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

One-click install

Cursor deeplink config payload

{
  "url": "https://keyid.ai/mcp"
}

Identity behavior

The remote Cursor install stores a managed KeyID identity for that connector, so inbox, OTP, and saved secrets persist across sessions.

The local Cursor install runs npx -y @keyid/agent-kit inside your environment, so identity persistence depends on how you store the keypair.

For agent signup tasks, pair KeyID with explicit prompts that tell Cursor when to start a signup session, when to save browser state, and when to avoid guessing on ambiguous artifacts.

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 Vercel before I paste the email into the form.
  • Wait for the Vercel session artifact and return only the best link or code.
  • Store the final browser state and session cookie after the dashboard loads.
  • Record this registration under serviceName Vercel with the username and completed session state.
  • If the message matches multiple sessions, stop and tell me what service or sender filter to tighten.

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. `wait_for_registration_artifact` — Poll a signup session until an artifact arrives or the session expires, blocks, or times out.
  4. `save_browser_state` — Store cookies and browser session state for a signup session in the KeyID vault.
  5. `put_secret` — Create or update a vault entry.
  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 the Cursor deeplink opens but does not install, paste the config JSON manually into Cursor MCP settings.
  • If the remote install loops on auth, revoke the existing install, reconnect, and finish the OAuth redirect once.
  • If a service mixes email codes and TOTP, set expectedArtifactTypes on the signup session before waiting so Cursor does not guess the wrong artifact.