Model Context Protocol

MCP Server

Connect AI agents (Claude, Cursor, Cline…) to CoolMail via Model Context Protocol: the agent creates the inbox, waits for the email and reads the verification code — no dashboard, no copy-paste.

Endpoint

POST https://coolmail.click/api/v1/mcp

Authentication

Bearer cmk_live_… (the same key as the REST API)

Tools

create_inboxcreates an inbox (debits R$5 from the balance — the MCP client asks for your confirmation; max 100/day per key). Optional params: alias and domain (pool TLD, same price — the tool description lists the available domains)

list_inboxeslists the account's inboxes

wait_for_emaillong-polls for up to 25s waiting for a verification code to arrive in the inbox

get_messagereads the full content of a message (text body, code and links)

extract_otpextracts just the verification code from a message

extract_linksextracts links from a message (best-guess verification link first)

Set up your client

Add a custom MCP connector pointing to the endpoint with your key in the Authorization header. Example config (Cursor / Cline):

mcp.json

{
  "mcpServers": {
    "coolmail": {
      "url": "https://coolmail.click/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer cmk_live_SUA_CHAVE"
      }
    }
  }
}

Limits

Each key only sees its own account's data — same isolation as the REST API.
120 req/min per key; creation 10/min and 100/day; wait_for_email 30/min.
wait_for_email holds for up to 25s per call — no code in time, the agent simply calls again.