KeyID
Give your agent managed signup sessions, inbox/SMS hooks, and OTP/TOTP handling so it can test real account flows without you juggling browsers and codes manually.
Overview
KeyID is a MCP server for the Build phase that supplies signup sessions, browser continuity, and email/SMS plus OTP/TOTP infrastructure so AI agents can run real verification flows.
What is this MCP server?
- Signup session orchestration with browser continuity for agent-driven flows
- Email and SMS plumbing plus OTP and TOTP handling for verification steps
- npm package @keyid/agent-kit with npx runtime hint and optional remote streamable-http endpoint
- Hosted MCP at keyid.ai/mcp alongside stdio local integration
- Catalog version 0.2.10 with GitHub source KeyID-AI/KeyID
- MCP catalog version 0.2.10
- npm identifier @keyid/agent-kit with npx runtime hint
- Remote MCP endpoint documented at https://keyid.ai/mcp (streamable-http)
What problem does it solve?
Agents that test signups stall on email links, SMS codes, and TOTP unless you manually copy secrets or maintain fragile browser hacks.
Who is it for?
Indie builders automating staging signups, onboarding QA, or agent demos that require real email/SMS and one-time codes.
Skip if: Products that only need static API keys with no user signup, or teams forbidden from third-party identity/session services.
What do I get? / Deliverables
After you add KeyID, your agent can hold signup sessions and resolve OTP/TOTP steps through MCP tools instead of you acting as the verification bottleneck.
- MCP-accessible signup sessions with browser continuity for agents
- Tooling paths for email, SMS, OTP, and TOTP resolution during automated flows
- Repeatable agent-driven verification without manual code copying
Recommended MCP Servers
Journey fit
KeyID is infrastructure you wire in while building agent-driven products that need real signup and verification paths, so Build → integrations is the canonical shelf. Email, SMS, OTP/TOTP, and browser continuity are third-party identity channels you integrate—not core app UI or backend CRUD alone.
How it compares
Agent signup and OTP infrastructure MCP, not a hosted auth product you ship to end users by itself.
Common Questions / FAQ
Who is KeyID for?
It is for developers building or testing apps with AI agents that must complete signup, email verification, SMS, or authenticator-style OTP/TOTP steps.
When should I use KeyID?
Use it during build and integration when automated flows need persistent sessions and real verification channels—not when you only mock auth in unit tests.
How do I add KeyID to my agent?
Add the MCP server via npx @keyid/agent-kit for stdio in Claude Code or Cursor, or configure the remote streamable-http URL https://keyid.ai/mcp per your host’s MCP settings.