InboxPlease MCP Server Deliverability Tools for AI Agents
Connect Claude, ChatGPT and any MCP client to InboxPlease. Agents can monitor warmup and pause or resume it, run inbox placement tests, analyse emails, read Domain Health, get a deliverability overview, analyse domains and send email (opt-in).
Available on: Enterprise# Connect InboxPlease to Claude Code claude mcp add --transport http inboxplease \ https://api.inboxplease.com/mcp \ --header "Authorization: Bearer inp_YOUR_API_KEY"
What is MCP Server?
The InboxPlease MCP server is a Model Context Protocol endpoint that lets AI agents call InboxPlease tools using a scoped API key: a deliverability overview, Domain Health results and scan history, warmup status and stats with pause and resume, inbox placement tests (manual or from a connected mailbox), email analysis, domain analysis and profiles, reputation and SEO/GEO metrics, mailbox tools, and opt-in sending and message tools. Every developer scope is opt-in. Tools that change something tell the agent to confirm with you first, sending is a separate owner/admin scope, and every send is staged as a preview that needs explicit confirmation.
- MCP over Streamable HTTP
- Claude, ChatGPT, any MCP client
- Overview, warmup, placement, analysis, domains, mailboxes, email
- inp_ API key with /mcp/ scope
- 300 requests/min · 10 concurrent calls per key
- Opt-in scope · two-phase preview → confirm
- Enterprise
Safe by default
Scoped keys
Restrict each key to specific tools and sender addresses.
Send is opt-in
The send scope must be explicitly requested at key creation. It's never granted by default.
Preview before send
send_email stages a preview and single-use token. Nothing is sent until confirm_send.
Recipient quotas
Per key, per mailbox and per organization limits — max 5 recipients per send.
Human in the loop
Connecting a mailbox returns an OAuth link a person must open.
Audited
Every staged send is recorded with each state change.
Owner/admin for actions
Sending, connecting mailboxes, pausing warmup and starting placement tests need a key created by an owner or admin.
Prompt-injection safeguard
Content an attacker could control (email bodies, headers, subjects) is labelled as untrusted in tool output.
Per-key rate limits
300 requests/min and at most 10 calls running at once per key. Every call is recorded per key.
Built with InboxPlease: Outreach Please
Outreach Please is a reference outreach app built only on the public REST API and this MCP server. Its server holds the inp_ key, stages every send and confirms it only after a person approves the preview, and checks Domain Health before a campaign goes out, with an optional placement test.
See how Outreach Please is builtTools agents can call
Questions about MCP Server
Can AI agents like Claude use InboxPlease?
Yes. On Enterprise, the InboxPlease MCP server lets Claude, ChatGPT and other MCP clients get a deliverability overview, read Domain Health results and scan history, monitor warmup and pause or resume it, run inbox placement tests, analyse emails, run domain analysis, domain profiles, reputation scores and SEO/GEO checks, and check connected mailboxes, all with a scoped API key. Actions need opt-in scopes on an owner/admin key, and the agent confirms with you first. Sending is opt-in, previewed first and audited.
Can an agent pause my warmup or start placement tests?
Only if you allow it. Pausing or resuming warmup and starting placement tests each need an opt-in scope ticked when the key is created, and those scopes only work on a key created by an owner or admin of your organization. The agent is also told to confirm with you before it acts.
Can an agent read my inbox?
No agent can browse or search your inbox, and mailboxes you connect through our standard app are send-only. If you tick the separate read scope on an owner/admin key, read_email can fetch one message whose ID the agent already has, but only from a mailbox connected over IMAP. Its content is labelled as untrusted.
Works well with
All features →Connect your agent
MCP access is available on Enterprise.