Model Context Protocol

Give your AI agent a real inbox to work with

MailParrot ships a hosted MCP server so Claude, Cursor, ChatGPT, and any other MCP-aware model can create disposable inboxes, wait for mail to arrive, and pull out OTPs, magic links, and auth codes-all with tool calls, no human checking email.

Get an API key for free Full MCP reference

1,000 free credits, no card required

Point your MCP client at MailParrot

Add this to your Cursor mcp.json (or any MCP-compatible client config). Swap in your own API key.

mcp.json

{
  "mcpServers": {
    "mailparrot": {
      "url": "https://api.mailparrot.app/mcp",
      "headers": {
        "x-api-key": "mp_your_key_here"
      }
    }
  }
}

Staging: https://api.test.mailparrot.app/mcp. Authorization: Bearer mp_… also works instead of the x-api-key header.

Get an API key with 1,000 free credits

No credit card, no sales call-just sign up and go.

1
Sign up for free
Create an account with Google sign-in. Every new account gets 1,000 credits automatically-no credit card required.
2
Create an API key
Open Dashboard → Settings → API Keys and click Create key. Give it a name like "AI agent" and copy the value-it's only shown once.
3
Paste it into your MCP config
Drop the key into the x-api-key header below and point your MCP client at the hosted URL. That's it-no local install, no build step.

What your agent can do

The MCP server exposes the same projects, aliases, messages, and webhooks tools as the REST API-just as callable tools your model can invoke directly. See the full tool list for every operation.

Spin up inboxes on demand

create_project and create_alias give your agent a real, working email address like qa@to.mailparrot.app in one tool call-no dashboard clicks required.

Read the OTP back

wait_for_auth_code polls until a code, magic link, or OTP arrives and hands it straight back to the model-no human ever opens an inbox.

Check credits before it runs out

get_usage lets an agent confirm it has budget left before kicking off a flow, and self-serves the upgrade link if it doesn't.

Wire up webhooks too

create_webhook and list_webhook_logs let an agent hand off to event-driven automation instead of polling, and debug deliveries when something looks off.

Use cases for MailParrot as an AI model MCP

Any agent that needs a real inbox-and a way to read what lands in it-can use MailParrot. Here's where teams are plugging it in.

Autonomous QA & coding agents

Cursor, Claude Code, and other coding agents can create a disposable inbox mid-session, run your signup flow, and pull the OTP or magic link needed to finish verifying it-no human needed to babysit the browser or check email.

Browser-use & computer-use agents

Agents that navigate the web on your behalf-booking, account creation, research-need an email address to complete signups. MailParrot hands them one instantly, plus a tool to read the verification email straight back.

CI/CD & release-gate agents

An agent embedded in your pipeline can create a project-scoped inbox per build, exercise the auth flow, and fail the build automatically if no code arrives-no one watching a mailbox while the merge queue runs.

Synthetic monitoring copilots

A scheduled agent can periodically simulate a signup or login against production, confirm the OTP lands inside your SLA, and alert your team on drift before real customers notice something is broken.

Support & ops copilots

Debugging an "I never got my code" ticket? A support copilot can call get_latest_auth_code or list_messages on the customer's alias, see exactly what was parsed, and self-serve an answer instead of escalating.

Multi-agent test-data generation

Orchestrated multi-agent systems that need many independent identities-one per sub-agent or scenario-can create and delete aliases on the fly, keeping test data isolated across parallel runs.

Credits work the same over MCP

Each incoming email costs 1 credit, whether it's triggered by a human, a test script, or an AI agent. When credits hit zero, inbound mail stops being stored and list_messages / wait_for_auth_code return a PAYMENT_REQUIRED payload with a link to top up-project, alias, and get_usage tools keep working so the agent can recover on its own.

See the MCP server docs for the full tool reference, or the pricing page for credit pack sizes.

Connect your first agent in minutes

1,000 free credits with every account-no card required. They don't expire.

Get started for free