Email Inbox API + Sending by Sendmux

Name: Email Inbox API + Sending by Sendmux
Author: Sendmux

作者：Sendmux版本 2.2.0i★ –i电脑或云端

注册名称io.github.Sendmux/sendmux-mcp

安装

概览

作者提供的说明（英文原文）

AI email inbox and sending tools with attachments, search, live events, and webhooks.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://mcp.sendmux.ai/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "sendmux": {
      "command": "npx",
      "args": [
        "-y",
        "sendmux-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http sendmux https://mcp.sendmux.ai/mcp

或者在你的电脑上运行

claude mcp add sendmux -- npx -y sendmux-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "sendmux": {
      "url": "https://mcp.sendmux.ai/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "sendmux": {
      "command": "npx",
      "args": [
        "-y",
        "sendmux-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "sendmux": {
      "type": "http",
      "url": "https://mcp.sendmux.ai/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "sendmux": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sendmux-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://mcp.sendmux.ai/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Sendmux 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“聊天与邮件”中的其他服务器比较i

星标数多于此分类中其他 1771 个服务器的 0%
发布到注册中心的时间比此分类中其他 1771 个服务器的 43% 更新
基础检查结果等于或优于此分类中其他 1771 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Email Inbox API + Sending by Sendmux 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.2.0）于36天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

作者：Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

在云端运行★ 2,949Apache-2.02个月前更新

安装

emailmd

作者：anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

电脑或云端★ 1,385MIT31天前更新

安装

MCP WhatsApp Cloud

作者：codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

在你的电脑上运行★ 277MIT5个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Email Inbox API + Sending by Sendmux

Email inbox API, inbound mail, and outbound sending MCP and A2A servers for AI agents, with inbound email, clean JSON parsing, webhooks, and multi-provider routing through Sendmux.

This package is the Sendmux MCP. Keep it separate from any documentation-search MCP used by docs tooling.

Documentation

Sendmux docs: sendmux.ai/docs
Management API reference: sendmux.ai/docs/api/introduction
Mailbox API reference: sendmux.ai/docs/mailbox-api/introduction
Sending API reference: sendmux.ai/docs/sending-api/introduction
Source repository: qubrics/qubrics-sdk

Requirements

Python 3.10 or newer.
A send-capable smx_mbx_* key or owner-approved Sending-resource smx_agent_* token for Sending tools.
A mailbox-scoped smx_mbx_* key or scoped smx_agent_* token for Mailbox tools.
A root smx_root_* key for Management tools.

2.0.0 upgrade

Version 2.0.0 removes local file_path and roots inputs from MCP attachment tools. Before upgrading a self-managed package or server, retain the prior known-working package environment, dependency state, and MCP client and tool configuration. Update attachment callers to use the attachment workflow for agents, then verify tool discovery and each attachment workflow your agents use.

To roll back a self-managed installation, restore the retained package environment, dependency state, and MCP client and tool configuration together. Verify tool discovery and the relevant attachment workflow before resuming agents. A package rollback doesn't reverse uploads or sends that have already completed.

For clients that use Sendmux's hosted endpoint, changing a local pip environment doesn't change the deployed server version. A hosted deployment rollback is a separate operator release action and must be verified against the hosted endpoint.

Installation

pip install sendmux-mcp

Usage

Run a single local server with the per-surface commands.

QUBRICS_API_KEY=smx_mbx_... sendmux-mcp-mailbox

QUBRICS_API_KEY=smx_root_... sendmux-mcp-management QUBRICS_API_KEY=smx_mbx_... sendmux-mcp-sending

Run a combined local server with sendmux-mcp.

QUBRICS_MCP_SURFACES=mailbox,sending \

QUBRICS_MAILBOX_API_KEY=smx_mbx_... \ QUBRICS_SENDING_API_KEY=smx_mbx_... \ sendmux-mcp

Run all three local surfaces when you have both key types.

QUBRICS_MCP_SURFACES=mailbox,management,sending \

QUBRICS_MAILBOX_API_KEY=smx_mbx_... \ QUBRICS_MANAGEMENT_API_KEY=smx_root_... \ QUBRICS_SENDING_API_KEY=smx_mbx_... \ sendmux-mcp

The generic sendmux-mcp command also accepts --surface or --surfaces. The wrapper commands select exactly one surface.

Transports

stdio is the default transport for local agent clients.

QUBRICS_API_KEY=smx_mbx_... sendmux-mcp-mailbox --transport stdio

http and streamable-http expose the MCP endpoint over HTTP. HTTP mode defaults to 127.0.0.1:8765/mcp and requires a separate MCP bearer token unless you explicitly opt out.

QUBRICS_API_KEY=smx_mbx_... \

QUBRICS_MCP_HTTP_BEARER_TOKEN=local-mcp-token \ sendmux-mcp-mailbox --transport http --host 127.0.0.1 --port 8765 --path /mcp

/health returns a small JSON health response for the selected surfaces.

Hosted Endpoint

The public hosted MCP endpoint is https://mcp.sendmux.ai/mcp.

For hosted clients, use HTTP transport with OAuth. Do not add manual Authorization headers, API keys, custom OAuth endpoints, or custom scopes unless your client explicitly requires them.

Hosted OAuth clients that omit requested scopes during registration or authorization are supported; the server advertises the hosted scope set through discovery and bearer challenges.

The packaged sendmux-mcp-hosted command runs the hosted server runtime. Local and private deployments should use the local commands above unless you are operating a compatible OAuth-backed hosted environment.

Hosted A2A Endpoint

The same hosted runtime exposes deterministic A2A 1.0 over HTTP+JSON at https://a2a.sendmux.ai/a2a/v1. Discover it from https://a2a.sendmux.ai/.well-known/agent-card.json; OAuth resource metadata is at https://a2a.sendmux.ai/.well-known/oauth-protected-resource.

Send exactly one JSON DataPart to the A2A message:send operation. Its data selects a curated Sendmux operation and supplies that operation's inputs:

"operationId": "managementListDomains", "pathParameters": {}, "query": { "limit": 10 }, "headers": {}, "body": null, "mailboxId": null }

operationId uses the same curated operation IDs as the hosted MCP service. OAuth grants are audience-bound to the A2A resource and retain their Sendmux surface and permission limits. The service returns one JSON DataPart containing the upstream status, safe response headers, and JSON body (or bodyBase64 for non-JSON responses).

The A2A endpoint is immediate and stateless: streaming, push notifications, persistent tasks, and task cancellation are not advertised or routed.

Configuration

Setting	Environment	Default
Tool surfaces	`QUBRICS_MCP_SURFACES`	required for `sendmux-mcp`; wrapper commands select one surface
API key fallback	`QUBRICS_API_KEY`	accepted for compatible single-key setups
Mailbox API key	`QUBRICS_MAILBOX_API_KEY`	required when mailbox is selected unless a compatible fallback is provided
Management API key	`QUBRICS_MANAGEMENT_API_KEY`	required when management is selected unless a compatible fallback is provided
Sending API key	`QUBRICS_SENDING_API_KEY`	required when sending is selected unless the fallback key is a send-capable `smx_mbx_` key or owner-approved Sending-resource `smx_agent_` token
App API base URL	`QUBRICS_APP_BASE_URL`	`https://app.sendmux.ai/api/v1`
Sending API base URL	`QUBRICS_SENDING_BASE_URL`	`https://smtp.sendmux.ai/api/v1`
Transport	`QUBRICS_MCP_TRANSPORT`	`stdio`
HTTP host	`QUBRICS_MCP_HOST`	`127.0.0.1`
HTTP port	`QUBRICS_MCP_PORT`	`8765`
HTTP path	`QUBRICS_MCP_PATH`	`/mcp`
HTTP bearer token	`QUBRICS_MCP_HTTP_BEARER_TOKEN`	required for HTTP unless opt-out is enabled
Allow unauthenticated HTTP	`QUBRICS_MCP_ALLOW_UNAUTHENTICATED_HTTP`	`false`
Allowed browser origins	`QUBRICS_MCP_ALLOWED_ORIGINS`	no browser origins
Snapshot directory override	`QUBRICS_MCP_OPENAPI_INPUT_DIR` or `OPENAPI_INPUT_DIR`	packaged snapshots
App snapshot override	`QUBRICS_MCP_APP_OPENAPI`	packaged app snapshot
Sending snapshot override	`QUBRICS_MCP_SENDING_OPENAPI`	packaged sending snapshot
Request timeout	`QUBRICS_MCP_TIMEOUT_SECONDS`	`30`
Retry attempts	`QUBRICS_MCP_RETRY_MAX_ATTEMPTS`	`3`
Retry time budget, in seconds	`QUBRICS_MCP_RETRY_MAX_ELAPSED_SECONDS`	unset

Retries honour Retry-After and X-RateLimit-Reset without applying the local backoff ceiling, and stop for retryable: false. Set the optional retry budget with RetryConfig(max_elapsed_seconds=30), the environment variable above, or --retry-max-elapsed-seconds 30. A retry that would exceed the remaining budget returns the original error; in-flight requests keep their normal HTTP timeouts.

Packaged OpenAPI snapshots are the default so released tool names, schemas, and descriptions stay stable. Path, directory, and URL overrides are available for development, canary, and debugging runs.

Tool Surfaces

Mailbox: tools for granted mailboxes, profile/session discovery, messages, attachments, bounded message waits, threads, folders, search, counts, and mailbox sends. Requires an smx_mbx_* key or scoped smx_agent_* token. Agent tokens remain limited by server-side scopes; pre-claim self-registered agent tokens do not include email.send.
Management: tools for domains, mailboxes, logs, metrics, spend summary, and webhooks. Requires an smx_root_* key.
Sending: tools for attachment upload refs, single sends, and batch sends. Requires an smx_mbx_* key or owner-approved Sending-resource smx_agent_* token.

The server rejects keys with the wrong prefix before starting.

Package Contract For Maintainers

The source checkout includes sendmux_mcp/mcp-contract.json, generated from the actual server factory's public tool discovery. Use its tools.by_surface entries and tools.count instead of maintaining a separate catalogue. Each entry retains the tool's description, input/output schemas, and annotations. The contract also separates hosted resource, local transports, API origins, certified protocol revisions, and the runtime versions used during generation.

After installing a build that contains the contract, read it without credentials or network requests:

from sendmux_mcp.contract import load_contract

contract = load_contract() print(contract["package"])

The result identifies the installed distribution and version. load_contract() raises ValueError for stale source/version evidence, a mismatched pinned FastMCP runtime, or unsupported certified revisions. The recorded transitive MCP version is provenance, not a narrower dependency constraint. Reading the artifact does not certify a newly resolved dependency version or prove a deployed service matches this build.

uploads distinguishes the locally enforced inline and Mailbox byte caps from Sending's returned max_size_bytes authority. The Sending presign request schema does not impose a numeric maximum; use the upload intent response, not a historical source constant. URL expiry and physical attachment retention are not equivalent, and this artifact does not certify storage cleanup.

From the repository root, pnpm generate:mcp refreshes native editable metadata and writes deterministic contract bytes. With that environment prepared, pnpm exec .tmp/python-venv/bin/python -m sendmux_mcp.contract --check checks freshness without rewriting. pnpm build:mcp verifies tests, wheel/sdist inclusion, installed consumption, and frozen conformance checks. Checkout changes are not available through pip install until their release is published.

Attachment Workflow For Agents

Use qubrics_mailbox_wait_for_message when a user asks an agent to wait for new mail. The tool is bounded; if it returns matched=false, call it again rather than holding an MCP tool call open indefinitely.

When a message has attachments:

Call qubrics_mailbox_read_attachment with message_id and attachment_id when you need the attachment contents.
For small text-like attachments, read the returned text.
For binary or oversized attachments, use the returned resource_link / download_url promptly outside model context.
Use qubrics_mailbox_get_attachment only when metadata is enough or you need to refresh the link.

Use qubrics_mailbox_upload_attachment for outbound attachments over MCP. It accepts exactly one input mode:

presign_upload_url=true for hosted MCP or shell-capable agents; upload the file to the returned URL with exact headers and no API key, then send with the returned blob_id.
content_base64 only for tiny agent-authored files, capped at 32 KiB decoded. If it is

只显示了开头部分；其余内容请在仓库中阅读

Email Inbox API + Sending by Sendmux

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“聊天与邮件”中的其他服务器比较i

常见问题

替代选择

Vexa

emailmd

MCP WhatsApp Cloud

作者的 README

Email Inbox API + Sending by Sendmux

Documentation

Requirements

2.0.0 upgrade

Installation

Usage

Transports

Hosted Endpoint

Hosted A2A Endpoint

Configuration

Tool Surfaces

Package Contract For Maintainers

Attachment Workflow For Agents