https://inbound.new/mcp
Connect
With OAuth (recommended)
Add the URL to your client. When it connects, it opens Inbound in your browser; sign in and approve access. No API key needed.With an API key
For scripts and clients without OAuth, send an API key from settings as a bearer token: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
- 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. - Connect the agent to
https://inbound.new/mcpwithAuthorization: Bearer <mailbox password>. - 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.
*.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
- “Show me unread email to support@mydomain.com”
- “Create a webhook endpoint for https://example.com/hooks and route orders@mydomain.com to it”
- “Create a mailbox for agent@mydomain.com and give me its MCP config”
- “Reply to the last email from jane@example.com saying we’ll ship Friday”
- “Block cold sales outreach with a Guard rule”