MCP server (AI coding agents)

InboxDome runs a hosted Model Context Protocol server at https://inboxdome.com/mcp. Connect it and your coding agent can test signup and OTP flows against the app it is building, with real email and no mocks.

Claude Code

claude mcp add --transport http inboxdome https://inboxdome.com/mcp \
  --header "Authorization: Bearer idk_live_..."

Any MCP client (JSON config)

{
  "mcpServers": {
    "inboxdome": {
      "type": "http",
      "url": "https://inboxdome.com/mcp",
      "headers": { "Authorization": "Bearer idk_live_..." }
    }
  }
}

Tools

Tool	What it does
`create_inbox`	New temporary address (optionally on a chosen domain)
`wait_for_email`	Long-poll for the next email or OTP (up to 50s per call)
`list_messages` / `get_message`	Read what arrived: body, links, OTP, SPF/DKIM/DMARC
`run_assertions`	Wait + verify content, OTP, link responds, auth results
`delete_inbox` / `list_domains`	Cleanup and domain discovery

A typical agent flow: create_inbox → fill the signup form with the address →wait_for_email with waitFor: "otp" → submit the code →run_assertions on the welcome email.

No API key yet?

Connecting without a key still works: the server initializes and lists its tools, so you (or your agent) can inspect it first. The first tool call then explains how to self-register. An agent can get its own free key without leaving the session:

curl -X POST https://inboxdome.com/v1/accounts \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com"}'
# → { "apiKey": "idk_live_..." }  (free plan, 100 inbox tests/month)

Reconnect with Authorization: Bearer <apiKey> and every tool works. The key is shown once; store it.

Rate limits and usage are the same as your API plan.

InboxDome is for testing applications you own or are authorized to test; see theAcceptable Use Policy.

API reference →