Skip to main content
Inbound’s MCP (Model Context Protocol) server lets AI assistants manage your domains, endpoints, addresses, emails and Guard rules. It can also create mailboxes: virtual email accounts that an agent can read, reply from and send from. Server URL: https://inbound.new/mcp

Connect

Add the URL to your client. When it connects, it opens Inbound in your browser; sign in and approve access. No API key needed.
In Claude.ai and ChatGPT, add a custom connector with the same URL. OAuth grants full access to your account, the same as an API key. The approval screen names the app and where it will send you back to; only approve apps you started the connection from.

With an API key

For scripts and clients without OAuth, send an API key from settings as a bearer token:
The x-inbound-api-key header also works. Clients that only support STDIO can bridge with npx mcp-remote https://inbound.new/mcp --header "Authorization:Bearer ${INBOUND_API_KEY}".

Give an agent its own mailbox

  1. Ask your assistant to create a mailbox, e.g. “Create a mailbox for agent@yourdomain.com called Support Agent”. This calls create_mailbox, which returns a password shown once.
  2. Connect the agent to https://inbound.new/mcp with Authorization: Bearer <mailbox password>.
  3. The agent now has one email account: it can check its inbox, read, reply, send and archive. It can’t see other mail in your account or send as any other address. The Inbound API enforces this.
The same mailbox password works over IMAP and SMTP, and the mailbox appears in the dashboard. The address must be on a verified domain; new accounts can use their instant *.inbnd.dev domain.

Mailbox tools

Account tools

Connected with OAuth or an API key, the server exposes 50 tools: To expose fewer tools, add ?toolsets= with any of domains,endpoints,addresses,emails,mailboxes,guard, for example https://inbound.new/mcp?toolsets=mailboxes,emails.

Example prompts

The server is open source: inboundemail/mcp.