Skip to content

Maildeck API and MCP

Buy, set up and monitor cold-email infrastructure. Every operation here is also an MCP tool of the same name at /mcp. Authenticate with “Authorization: Bearer md_live_…”. The API never charges a card: buying returns a payment link for a person to pay. Writes take an idempotency_key; chargeable or irreversible actions also need confirm: true. Start with get_account_status.

Hand this to your AI One click copies a ready prompt with the whole API and MCP reference. Paste it into Claude, ChatGPT or Cursor.
Open llms.txt
RESThttps://api.maildeck.co/v1
MCP (Streamable HTTP)https://api.maildeck.co/mcp
OpenAPIhttps://api.maildeck.co/v1/openapi.json
For agentshttps://api.maildeck.co/v1/llms.txt

An agent that only has api.maildeck.co can read everything it needs from the following well-known documents. No key is required.

MCP server card (SEP-1649)https://api.maildeck.co/.well-known/mcp/server-card.json
API catalog (RFC 9727)https://api.maildeck.co/.well-known/api-catalog
OAuth protected resource (RFC 9728)https://api.maildeck.co/.well-known/oauth-protected-resource
OAuth authorization server (RFC 8414)https://api.maildeck.co/.well-known/oauth-authorization-server
OpenID Connect discoveryhttps://api.maildeck.co/.well-known/openid-configuration
Agent quickstarthttps://api.maildeck.co/auth.md

Most AI apps only need the MCP address. The app sends you to Maildeck to sign in, you choose what it may do, and no key is copied anywhere. It takes about two minutes.

  1. In Claude, open Settings → Connectors and choose Add custom connector.
  2. Name it Maildeck and paste the address https://api.maildeck.co/mcp.
  3. Choose Connect. Claude opens Maildeck: sign in and approve what it may do.
  4. In a new chat, ask: What is the status of my Maildeck account?
  • In the app: Settings → API & MCP → create a key and pick its scopes. The key is shown once.
  • From an agent: call start_connect with no key, show the person the link it returns, and call poll_connect until they approve. The key comes back once.
  • MCP apps (Claude, ChatGPT, Cursor, Claude Code): add the MCP address as a connector. The app signs the person in to Maildeck and they approve what it may do.

Send the key on every call: Authorization: Bearer md_live_….

ScopeLets the key
readSee the account, domains, orders, setup, masking and blacklist status; ask Maya
billingPrice orders and create payment links
writeSave order setup, finish setup, turn masking on or off, connect a sequencer or Calendly
  • Nothing is charged through the API. create_checkout returns a payment link for a person to pay. Pass the due_now_cents from quote_order as expected_due_now_cents, so a price change fails instead of charging something unexpected.
  • Every write takes an idempotency_key. Sending the same one again returns the first result.
  • confirm: true is required on create_checkout, complete_order_setup, enable_masking and disable_masking.
  • Logins and API keys go in, never out. Registrar, sequencer and DNS credentials can be saved; no call returns them.
  • Cancelling is done by a person in the app, not through the API.
  • Start with get_account_status. It lists what the account has and the next actions, most urgent first.

Errors come back as {"error": {"code": "...", "message": "..."}} with a matching HTTP status. The message is written to be shown to a person.