inboundemail/mcp

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

2 stars 0 forks Качество 68 Тренд 28

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

Обзор

Connect any MCP client (Claude, Cursor, OpenCode, ChatGPT, agents) to Inbound: manage domains, endpoints, addresses, emails, Guard rules and , which are virtual email accounts that agents can read and send from. https://inbound.new/mcp (Streamable HTTP, stateless) 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. Leave out headers to use OAuth.

README

Показан фрагмент оригинального README. Открыть оригинал.

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 " }
    }
  }
}

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: 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.

Give an agent its own inbox

Открыть полный README на GitHub

Установка

This server does not publish a one-line install command.

Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

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