Fetches keyid-agent-kit-mcp from aradotso/trending-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/keyid-agent-kit-mcp
Restart Cursor to activate keyid-agent-kit-mcp. Access via /keyid-agent-kit-mcp in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
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.
What It Does
Provisions a real email address for your AI agent automatically
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
npminstall @keyid/agent-kit
# oryarnadd @keyid/agent-kit
# or run directly without installingnpx @keyid/agent-kit
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):
# Run once to generate keys and register the agentnpx @keyid/agent-kit
# Keys are printed to stderr — save them!# Then set them in your environment or configexportKEYID_PUBLIC_KEY=<hex-from-output>exportKEYID_PRIVATE_KEY=<hex-from-output>
All 27 Tools Reference
Identity & Auth
keyid_provision — Register agent, get assigned email address
keyid_get_email — Get the current active email address
Messages
keyid_get_inbox — Fetch inbox; supports search query, filtering, pagination
keyid_send — Send email (to, subject, body, HTML, scheduled time, display name)
keyid_reply — Reply to a message by message_id
keyid_forward — Forward a message to another address
keyid_update_message — Mark read/unread, star/unstar
keyid_get_unread_count — Get count of unread messages
Threads & Drafts
keyid_list_threads — List conversation threads
keyid_get_thread — Get a thread with all its messages
keyid_create_draft — Save a draft
keyid_send_draft — Send a previously saved draft
Settings
keyid_get_auto_reply — Get current auto-reply/vacation responder config
keyid_set_auto_reply — Enable/disable auto-reply with custom message
keyid_get_signature — Get email signature
keyid_set_signature — Set email signature text/HTML
keyid_get_forwarding — Get forwarding rules
keyid_set_forwarding — Add or update forwarding to another address
Contacts
keyid_list_contacts — List all saved contacts
keyid_create_contact — Create a contact (name, email, notes)
keyid_delete_contact — Delete a contact by ID
Webhooks
keyid_list_webhooks — List configured webhooks
keyid_create_webhook — Register a webhook URL for inbound events
keyid_get_webhook_deliveries — View delivery history and failures
Lists & Metrics
keyid_manage_list — Add/remove addresses from allow or blocklist
keyid_get_metrics — Query usage metrics (sent, received, bounces)
Real Code Examples
Programmatic MCP Client (Node.js)
import{ spawn }from'child_process';import{ createInterface }from'readline';// Start the MCP server as a child processconst server =spawn('npx',['@keyid/agent-kit'],{env:{...process.env,KEYID_PUBLIC_KEY: process.env.KEYID_PUBLIC_KEY,KEYID_PRIVATE_KEY: process.env.KEYID_PRIVATE_KEY,},stdio:['pipe','pipe','inherit'],});// Send a JSON-RPC requestfunctionsendRequest(method, params ={}){const request ={jsonrpc:'2.0',id:Date.now(), method, params,}; server.stdin.write(JSON.stringify(request)+'\n');}// Read responsesconst rl =createInterface({input: server.stdout});rl.on('line',(line)=>{const response =JSON.parse(line);console.log('Response:',JSON.stringify(response,null,2));});// Initialize MCP sessionsendRequest('initialize',{protocolVersion:'2024-11-05',capabilities:{},clientInfo:{name:'my-app',version:'1.0.0'},});
Call a Tool via MCP JSON-RPC
// After initialization, call tools/callfunctioncallTool(toolName, toolArgs){const request ={jsonrpc:'2.0',id:Date.now(),method:'tools/call',params:{name: toolName,arguments: toolArgs,},}; server.stdin.write(JSON.stringify(request)+'\n');}// Get inboxcallTool('keyid_get_inbox',{limit:10});
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
