Skip to main content
Glama
Inbound Email MCP Server

Inbound Email MCP Server

by inboundemail

Inbound MCP server

Connect any MCP client (Claude, Cursor, OpenCode, ChatGPT, agents) to Inbound: manage domains, endpoints, addresses, emails, Guard rules and mailboxes, which are virtual email accounts that agents can read and send from.

Endpoint: https://inbound.new/mcp (Streamable HTTP, stateless)

Three ways to connect

Credential

What the agent gets

OAuth (just add the URL; the client opens Inbound to sign in)

All account tools, including creating mailboxes and acting as any of them

Account API key (from inbound.new/settings)

The same as OAuth, for scripts and clients without OAuth

Mailbox password (mail_…, returned by create_mailbox)

Only that mailbox: whoami, list_messages, read_message, update_message, get_thread, send_email, reply, download_attachment, plus the folder, folder-message, filter and spam tools, list_mailbox_activity and rotate_my_password. None take mailbox_id. Filters, spam settings, activity and password rotation each require their respective self_service flag (filters, spam, activity, password); otherwise the API returns 403.

The Inbound API enforces mailbox scopes and limits. An account can set protocols, allowed_ips, storage_quota_bytes, daily_send_limit and self_service with create_mailbox or update_mailbox. The password works as an MCP bearer token and for IMAP (imap.inboundemail.com:993) and SMTP (smtp.inboundemail.com:465) only where the protocol and IP are allowed. For MCP, the allowlist must include the MCP server's outgoing IP, not the agent's. Changing protocols, allowed IPs or self-service immediately closes open IMAP sessions. The daily limit counts only sends and replies authenticated by the mailbox password, not account-key sends.

{
  "mcpServers": {
    "inbound": {
      "type": "http",
      "url": "https://inbound.new/mcp",
      "headers": { "Authorization": "Bearer <api key or mailbox password>" }
    }
  }
}

Leave out headers to use OAuth. Discovery follows the MCP authorization spec: the 401 points to https://inbound.new/.well-known/oauth-protected-resource/mcp, the authorization server is https://inbound.new/api/auth (dynamic client registration, PKCE), and tokens carry the inbound:account scope for the https://inbound.new/mcp audience. This server verifies them against Inbound's JWKS and forwards them to the API.

x-inbound-api-key: <key> is also accepted. Clients that only speak STDIO can use npx mcp-remote https://inbound.new/mcp --header "Authorization:Bearer ${INBOUND_API_KEY}".

Limit the tool list

Add ?toolsets= (or an x-inbound-toolsets header) with any of domains,endpoints,addresses,emails,mailboxes,guard, e.g. https://inbound.new/mcp?toolsets=mailboxes,emails.

Related MCP server: Mail MCP Server

Give an agent its own inbox

  1. With the account key: create_mailbox { "address": "agent@yourdomain.com", "sending_name": "Support Agent" }.

  2. Give the returned password to the agent as its bearer token.

  3. The agent loops: list_messages { unread_only: true } → read_message → reply → update_message { is_archived: true }.

Mailboxes, read state and sent mail are stored by Inbound, so they show up in the dashboard and over IMAP too.

Tools (account key)

  • Domains: list_domains, get_domain, create_domain, update_domain, delete_domain, enable_domain_dkim

  • Endpoints: list_endpoints, get_endpoint, create_endpoint, update_endpoint, delete_endpoint, test_endpoint

  • Addresses: list_email_addresses, get_email_address, create_email_address, update_email_address, delete_email_address

  • Emails: list_emails, get_email, send_email, reply_to_email, update_email, cancel_scheduled_email, pause_scheduled_email, resume_scheduled_email, retry_email_delivery, list_threads, get_thread, list_attachments, download_attachment

  • Mailboxes: list_mailboxes, create_mailbox, update_mailbox, delete_mailbox, rotate_mailbox_password, get_mailbox, list_mailbox_messages, read_mailbox_message, update_mailbox_message, get_mailbox_thread, send_from_mailbox, reply_from_mailbox, download_mailbox_attachment

  • Mailbox folders: list_mailbox_folders, create_mailbox_folder, rename_mailbox_folder, delete_mailbox_folder

  • Folder messages (by folder path and UID, not account email ID): list_folder_messages, get_folder_message, get_folder_message_raw, set_message_flags, move_message, copy_message, delete_folder_message, expunge_folder, append_message, list_folder_message_attachments, download_folder_message_attachment

  • Mailbox filters: list_mailbox_filters, get_mailbox_filter, create_mailbox_filter, update_mailbox_filter, delete_mailbox_filter, reorder_mailbox_filters, apply_mailbox_filters. Enabled filters run on new received mail; use apply_mailbox_filters to process an existing folder.

  • Mailbox spam: get_mailbox_spam_settings, set_mailbox_spam_settings, add_spam_list_entry, remove_spam_list_entry. These affect only this mailbox, not the account verdict.

  • Mailbox activity: list_mailbox_activity reads one mailbox's log; list_account_activity reads across the account, optionally filtered by mailbox_id. Both list sign-ins, IMAP session events, quota errors and send failures, newest first. Events are retained for 30 days; message content and passwords are never logged.

  • Guard: list_guard_rules, get_guard_rule, create_guard_rule, update_guard_rule, delete_guard_rule, check_guard_rule, generate_guard_rule

Development

bun install
bun run dev        # http://localhost:5454/mcp, against production unless INBOUND_API_URL is set
bun run typecheck
INBOUND_API_KEY=... bun run stdio   # STDIO transport

Deployed on Vercel (team inbound, project inbound-mcp) as one function, api/mcp.ts. inbound.new/mcp rewrites to it from the main app.

Available Tools

14 tools
check_mailboxCheck MailboxA
Read-onlyIdempotent

Check your agent mailbox for incoming emails. Requires the x-inbound-mailbox header to be set. Returns emails sent TO your mailbox address, with unread emails shown first by default.

Inputs: status, limit, offset, time_range.

create_endpointCreate EndpointA

Create a new endpoint for receiving emails. Webhooks deliver emails as HTTP POST requests, email forwards send to another address.

Inputs: name (required), type (required), url, forwardTo, +2 more.

get_emailGet EmailA
Read-onlyIdempotent

Get detailed information about a specific email including full content, headers, attachments, and delivery status.

Inputs: id (required).

get_mailbox_threadsGet Mailbox ThreadsA
Read-onlyIdempotent

Get email threads/conversations for your agent mailbox. Shows conversations where your mailbox is a participant. Threads group related emails together like Gmail conversations.

Inputs: unread, limit, cursor.

get_threadGet ThreadA
Read-onlyIdempotent

Get a complete email thread (conversation) with all messages. Returns thread metadata, all messages in chronological order, and participant information.

Inputs: id (required).

list-domainslist-domainsD

No description provided

Inputs: no named parameters.

list_emailsList EmailsB
Read-onlyIdempotent

List emails in your Inbound account. Filter by type (sent, received, scheduled), status, time range, and more. Returns email metadata including sender, recipient, subject, and status.

Inputs: type, status, limit, offset, +2 more.

list_endpointsList EndpointsA
Read-onlyIdempotent

List all endpoints for receiving emails. Endpoints can be webhooks (HTTP delivery), email forwards, or email groups.

Inputs: type, active, limit, offset, +1 more.

list_threadsList ThreadsA
Read-onlyIdempotent

List email threads (conversations) in your inbox. Threads group related emails together like Gmail conversations. Returns thread metadata, participant list, and latest message preview.

Inputs: limit, cursor, search, unread.

reply_emailReply to EmailA

Reply to an email or thread. Accepts either an email ID or thread ID (replies to latest message in thread). Supports reply-all functionality to include original CC recipients.

Inputs: id (required), from (required), to, subject, +3 more.

reply_from_mailboxReply from MailboxA

Reply to an email from your agent mailbox. The 'from' address is automatically set to your mailbox address. Can reply to an email ID or thread ID (replies to latest message in thread).

Inputs: id (required), html, text, subject, +1 more.

retry_emailRetry Email DeliveryA

Retry delivery of a received email. Can retry to a specific endpoint, retry a specific failed delivery, or retry to all configured endpoints.

Inputs: id (required), endpoint_id, delivery_id.

send_emailSend EmailA

Send an email from your verified domain. Supports HTML and plain text content, CC/BCC, and scheduled sending with natural language times.

Inputs: from (required), to (required), subject (required), html, +6 more.

send_from_mailboxSend from MailboxA

Send an email from your agent mailbox. The 'from' address is automatically set to your mailbox address (x-inbound-mailbox header). Supports HTML/text content, CC/BCC, and scheduled sending.

Inputs: to (required), subject (required), html, text, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation3/5

    There is significant overlap between several tools, particularly list_emails vs check_mailbox (both list emails), list_threads vs get_mailbox_threads (both list threads), and send_email vs send_from_mailbox (both send emails). However, the descriptions help clarify some distinctions, such as check_mailbox focusing on unread emails and send_from_mailbox using a specific mailbox header.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., get_email, list_endpoints, reply_email), but there are minor deviations like list-domains (hyphenated) and retry_email (which uses 'retry' instead of a more standard verb like 'resend'). Overall, the naming is readable and mostly predictable.

    Tool Count4/5

    With 14 tools, the count is reasonable for an email management server, covering core operations like sending, receiving, listing, and replying. It's slightly on the higher side due to redundant tools, but still well-scoped for the domain without being overwhelming.

    Completeness5/5

    The tool set provides comprehensive coverage for email management, including CRUD-like operations (create_endpoint, list_endpoints), lifecycle handling (send, reply, retry), and domain management (list-domains). There are no obvious gaps; agents can fully interact with emails, threads, mailboxes, and endpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with access to PurelyMail's email management API, enabling user, domain, routing, and billing management through natural language.
      19
      43 npm
      13
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.
      16
      52 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI models to manage CloudMailin email data, including listing addresses, messages, and sending emails with markdown support.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and manage email via IMAP, and send emails with attachments via SMTP, using natural language commands.
      546 npm
      MIT