Give AI agents (Claude, Cursor) a real email address with 27 MCP tools for inbox, send, reply, contacts, search, and more via KeyID.ai

KeyID Agent Kit — MCP Email Tools for AI Agents Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection. KeyID Agent Kit gives AI agents (Claude, Cursor, or any MCP client) a real, working email address with 27 tools via the Model Context Protocol. No signup, no API keys to acquire manually, no cost. Powered by [KeyID.ai](https://keyid.ai). What It Does Provisions a real email address for your AI agent automatically Exposes 27 MCP tools: send, receive, reply, forward, search, contacts, drafts, webhooks, auto reply, signatures, forwarding rules, metrics Runs as a stdio MCP server — compatible with Claude Desktop, Cursor, and any MCP client Uses Ed25519 keypairs for identity — auto generated if not provided Installation Configuration Environment Variables Variable Description Default KEYID PUBLIC KEY Ed25519 public key (hex) Auto generated on first run KEYID PRIVATE KEY Ed25519 private key (hex) Auto generated on first run KEYID BASE URL API base URL https://keyid.ai Important: Save the auto generated keys after first run so your agent keeps the same email address across sessions. The keys are printed to stderr on first launch. Claude Desktop Setup Edit ~/Library/Application Support/Claude/claude desktop config.json (macOS) or %APPDATA%\Claude\claude desktop config.json (Windows): Cursor Setup In .cursor/mcp.json at project root or global Cursor settings: First Run — Get Your Email Address All 27 Tools Reference Identity & Auth Messages Threads & Drafts Settings Contacts Webhooks Lists & Metrics Real Code Examples Programmatic MCP Client (Node.js) Call a Tool via MCP JSON RPC Using with the MCP SDK (if building a custom client) Webhook Integration Common Patterns Pattern: Agent with Persistent Identity Pattern: Email Triggered Agent Loop Pattern: Draft Review Send Workflow Troubleshooting Agent gets a new email address every run Cause: Keys not persisted between runs. Fix: Save KEYID PUBLIC KEY and KEYID PRIVATE KEY from first run output and set them in your config or environment. MCP server not appearing in Claude Desktop Fix: Restart Claude Desktop after editing config. Verify JSON is valid (no trailing commas). Check that npx is in your PATH. Tool calls return errors Fix: Ensure the agent is provisioned first — call keyid provision before other tools, or call keyid get email to confirm the agent has an address. Emails not being received Fix: Check keyid manage list to ensure the sender isn't blocklisted. Check keyid get metrics for bounce data. Connection drops / server crashes Fix: The server uses stdio — make sure nothing else is writing to stdout in the same process. Restart the MCP server process. Keys auto generated but not shown Cause: stderr may be suppressed by your MCP client. Fix: Run npx @keyid/agent kit directly in a terminal first to capture the key output before adding to your MCP config. Protocol Details Transport: stdio (JSON RPC over stdin/stdout) MCP Protocol Version: 2024 11 05 Auth: Ed25519 keypair — public key becomes agent identity, private key signs requests Compatibility: Claude Desktop, Cursor, any MCP compatible client

keyid-agent-kit-mcp