OpenClaw

Give every OpenClaw agent its own email identity.

Add KeyID as a remote MCP skill so each agent in your fleet gets a real inbox, phone access, OTP/TOTP, and website verification — free at 1,000 accounts. Replaces paid ClawHub email skills.

Verification flows Open MCP hub Lovable guide
MCP-native skill Multi-agent fleet Email + verification Free at scale

OpenClaw setup

KeyID is a remote MCP server. OpenClaw treats every skill as an MCP server, so the integration is native — add the endpoint and your agents get email, SMS, and verification tools.

MCP config

Add to openclaw.json

// openclaw.json — add under mcpServers
{
  "mcpServers": {
    "keyid": {
      "url": "https://keyid.ai/mcp"
    }
  }
}

MCP config

Alternative: .mcp.json

// .mcp.json — same config, alternative path
{
  "mcpServers": {
    "keyid": {
      "url": "https://keyid.ai/mcp"
    }
  }
}

Migration

Replaces paid ClawHub email skills

KeyID replaces agent-mail and automated-ai-email-setup skills from ClawHub.

No API keys. No per-mailbox pricing.
Free at 1,000 accounts with real inboxes, phone/SMS, and OTP/TOTP.

Remove the old skill and add the KeyID MCP endpoint above.

When to use MCP, SDK, and multi-agent identity

OpenClaw treats every skill as an MCP server, so KeyID drops in as a native remote skill. Once connected, any agent in the fleet can provision its own inbox, read verification emails, handle OTP/TOTP, and store secrets — all through the standard MCP tool interface.

For multi-agent setups, each isolated agent gets its own KeyID identity. The Gateway routes messages to the right agent, and KeyID keeps each identity's inbox, phone number, and stored credentials separate. No shared state, no cross-agent leakage.

If a workflow needs browser automation — third-party signups, form fills, CAPTCHA-gated flows — let Playwright or a browser skill drive the page while KeyID owns the email address, verification codes, and durable registration state.

Copy-paste prompts

Use these in your OpenClaw agent configuration or skill definitions to wire up KeyID-backed email and verification.

  • Provision a KeyID identity for this agent and store the keys so the inbox persists across restarts.
  • Sign up for a new service using my KeyID email, wait for the verification email, extract the code, and complete registration.
  • Check my KeyID inbox for unread messages and summarize any verification or confirmation emails.
  • Use KeyID OTP/TOTP to complete two-factor authentication on the current login flow.
  • Save the session cookie and recovery codes from this signup back into KeyID secrets for next time.

Expected tool sequence

  1. `provision_identity` — create a durable KeyID identity for this agent with a real email address and optional phone number.
  2. `send_email` — send outbound email from the agent's provisioned address.
  3. `wait_for_message` and `get_verification_codes` — poll for verification emails or SMS and extract codes without custom polling logic.
  4. `follow_verification_link` — follow email verification links safely, or hand the browser step to Playwright when the site requires a live click path.
  5. `put_secret` and `save_registration` — store cookies, backup codes, TOTP seeds, and final registration state for recovery across sessions.

Failure and recovery notes

  • If the agent gets a fresh identity on every restart, persist KEYID_PUBLIC_KEY and KEYID_PRIVATE_KEY in the agent's environment or agentDir so the inbox survives across sessions.
  • If a paid ClawHub email skill is still active alongside KeyID, disable it to avoid duplicate inboxes and conflicting verification flows.
  • If verification polling times out, check that the sender domain and subject filter match the expected verification email before increasing timeouts.