developer

adbtd over MCP

Add adbtd as a Model Context Protocol server in Claude Code, Claude Desktop, Cursor, or any MCP-compatible agent. Your agent can list mailboxes, send mail, read deliverability metrics — without you wrapping the REST API by hand.

One server URL: https://mcp.adbtd.com. OAuth-based authorization, revocable from your dashboard at any time.

step 1

Add the server

One line in your agent's MCP config — see below per client.

step 2

Authorize in browser

On first connect, you'll be sent to adbtd to approve. We auto-mint an API key under your account with the agent's name attached.

step 3

Use the tools

Your agent can now call list_mailboxes, send_email, get_deliverability, and more.

Install

Claude Code

From your terminal:

claude mcp add --transport http adbtd https://mcp.adbtd.com

The --transport http flag is required — without it Claude Code assumes a stdio-based local server and fails to connect.

On first use, Claude Code opens your browser to complete the OAuth flow. Approve in your adbtd dashboard, and the connection is ready.

If you previously ran the command without the flag, remove the broken entry first: claude mcp remove adbtd.

Claude Desktop

Claude Desktop runs MCP servers locally. Use the mcp-remote bridge so it can speak to a remote HTTP server like ours. Edit your config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS; %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "adbtd": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.adbtd.com"]
    }
  }
}

Restart Claude Desktop. The first conversation that touches the server opens your browser for the OAuth flow.

Cursor

In ~/.cursor/mcp.json (or the per-project equivalent):

{
  "mcpServers": {
    "adbtd": {
      "url": "https://mcp.adbtd.com"
    }
  }
}

Other MCP-compatible agents

Any agent supporting MCP over Streamable HTTP can use https://mcp.adbtd.com. The server speaks OAuth 2.1 with Dynamic Client Registration — your agent will discover the auth server from the standard /.well-known/oauth-protected-resource metadata.

Agents that don't speak remote MCP natively can use the mcp-remote bridge shown above for Claude Desktop.

Tools

All tools are workspace-scoped — the OAuth token your agent holds binds it to one adbtd workspace. Cross-workspace access is impossible by construction. The set mirrors the customer-facing REST API one-for-one — anything you can do via /api/v1/* you can do via MCP.

tool	what it does
get_me	Workspace info + subscription state — equivalent to GET /v1/me.
list_mailboxes	List mailboxes, optionally filtered by domain or status.
get_mailbox	Fetch one mailbox by id.
create_mailbox	Provision a mailbox on a verified domain. Returns SMTP/IMAP details ready to use.
delete_mailbox	Hard-delete a mailbox by id. Irreversible — the maildir on disk is dropped.
send_email	Send mail through one of your mailboxes via SMTP submission.
list_messages	Fetch recent messages from a mailbox over IMAP. Paginated.
get_message	Fetch the full body + attachments of one message by IMAP UID.
list_domains	List domains on your workspace with SPF/DKIM/DMARC status.
add_domain	Add a (BYO) domain to your workspace. DNS records to publish are returned in list_domains.
delete_domain	Remove a domain and every mailbox on it. Irreversible.
list_ips	List dedicated IPs and their RBL listings.
add_ips	Order N additional dedicated IPs. May return a Stripe checkout URL if action is needed.
release_ip	Release a dedicated IP back to the pool. Releasing the last IP cancels the subscription.
get_deliverability	7d sent volume, avg spam score, top symbols, RBL status — same data as /dashboard/deliverability.

Authorization

Auto-provisioned. You never paste an API key. The first time your agent connects, your browser opens to adbtd.com/oauth/authorize — you approve, and we mint a key under your account.
Visible in your dashboard. Every connection shows up in /dashboard/api-keys under "mcp connections" with the agent's self-reported name (e.g. "Claude Code").
Revoke any time. "Disconnect" flips a flag — the very next MCP call from that agent returns 401. No restart, no propagation delay.
Workspace-scoped. The token binds to one workspace. An agent can never see, list, or act on data belonging to another workspace, even by trying.
Standards-based. OAuth 2.1 + Dynamic Client Registration + PKCE (S256 only). See /.well-known/oauth-authorization-server.
Treat the access token like a password. It lives in your agent's local config — never paste it into chat windows, issue trackers, or public scripts. If it leaks, disconnect it from the dashboard and re-authorize.

Pricing

No separate price for MCP. Your workspace's existing per-mailbox + per-IP subscription covers MCP usage the same way it covers REST API and IMAP/SMTP access — see pricing.