Integrations

MCP server

Connect Cursor (or any MCP client) to MailParrot over a hosted Streamable HTTP endpoint. No local package, Node install, or compile — just a URL and an API key.

New to MCP? See what AI agents can do with MailParrot and copyable connection config.

Point and go

Add this to your Cursor mcp.json. Create an API key in Dashboard → Settings.

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

Staging: https://api.test.mailparrot.app/mcp. Alias domains: to.mailparrot.app (prod) / to.test.mailparrot.app (staging). Authorization: Bearer mp_… also works.

Agent flow

Call get_usage to confirm credits remain.
Create a project and alias (create_project, create_alias).
Send the app under test to the returned inbox address.
Call wait_for_auth_code (or list_messages) to retrieve the OTP.

Credits and payment gating

When remaining credits hit zero, inbound mail is not stored, and the messages and latestAuthCode GraphQL operations fail with PAYMENT_REQUIRED. Project, alias, webhook, and usage tools still work. Buy packs in Settings → Credits.

See also the messages and latestAuthCode API reference.

Tools

get_usage, list_credit_packs
Projects: list_projects, create_project, update_project, delete_project
Aliases: list_aliases, create_alias, set_alias_active, delete_alias
Messages: list_messages, get_latest_auth_code, wait_for_auth_code
Webhooks: list_webhooks, create_webhook, update_webhook, delete_webhook, list_webhook_logs