MCP (Model Context Protocol) server for the Inbound Email API. Give your AI agent its own email address to send, receive, and manage emails.
The primary use case is giving an AI agent its own email identity. Set the x-inbound-mailbox header to your agent's email address:
{
"mcpServers": {
"inbound": {
"url": "http://localhost:5454/mcp",
"headers": {
"x-inbound-api-key": "your-api-key",
"x-inbound-mailbox": "Support Agent <support@yourdomain.com>"
}
}
}
}The header supports both formats:
- With display name:
Support Agent <support@yourdomain.com> - Email only:
support@yourdomain.com
| Tool | Description |
|---|---|
check_mailbox |
Check incoming emails for your mailbox (defaults to unread) |
get_mailbox_threads |
Get conversation threads where your mailbox is a participant |
send_from_mailbox |
Send emails - from is automatically set to your mailbox |
reply_from_mailbox |
Reply to emails/threads - from is automatically set to your mailbox |
- Check for new emails:
check_mailboxreturns unread emails with IDs - Read email details: Use
get_emailwith the email ID to read full content - Reply to emails:
reply_from_mailboxsends replies with your agent identity - Send new emails:
send_from_mailboxsends emails as your agent
When sending, the display name (e.g., "Support Agent") is included so recipients see a friendly sender name.
npm install @inbound/mcp
# or
pnpm add @inbound/mcp
# or
bun add @inbound/mcpAdd to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"inbound": {
"command": "npx",
"args": ["-y", "@inbound/mcp"],
"env": {
"INBOUND_API_KEY": "your-api-key",
"INBOUND_MAILBOX": "Agent <agent@yourdomain.com>"
}
}
}
}Start the server:
npx @inbound/mcp start:httpThen configure your client:
{
"mcpServers": {
"inbound": {
"url": "http://localhost:5454/mcp",
"headers": {
"x-inbound-api-key": "your-api-key",
"x-inbound-mailbox": "Agent <agent@yourdomain.com>"
}
}
}
}The MCP server authenticates using your Inbound API key:
- Environment variable:
INBOUND_API_KEY - HTTP header:
x-inbound-api-key
To restrict all operations to a single domain:
- Environment variable:
INBOUND_DOMAIN - HTTP header:
x-inbound-domain
check_mailbox- Check incoming emails for your mailboxget_mailbox_threads- Get conversation threads for your mailboxsend_from_mailbox- Send an email from your mailboxreply_from_mailbox- Reply to an email from your mailbox
list_emails- List sent, received, and scheduled emailsget_email- Get detailed information about a specific emailsend_email- Send or schedule an emailreply_email- Reply to an email or threadretry_email- Retry delivery of a failed email
list_threads- List email conversationsget_thread- Get all messages in a thread
list_domains- List all domains in your account
list_endpoints- List webhook and email forwarding endpointscreate_endpoint- Create a webhook, email forward, or email group endpoint
getting-started- Learn how to use Inbound Email API
# Install dependencies
pnpm install
# Run in development mode
pnpm dev
# Build for production
pnpm buildApache-2.0