Productivity · Remote MCP server
Email Inbox API + Sending by Sendmux
AI email inbox and sending tools with attachments, search, live events, and webhooks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Sendmux/sendmux-mcp- Version
- 2.2.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm, PyPI
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- Sendmux (GitHub)
- Website
- sendmux.ai/docs/guides/mcp
- Repository
- github.com/Sendmux/sendmux-sdk (folder packages/python/mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.sendmux.ai/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | sendmux-mcp | 1.0.0 | stdio |
| PyPI | sendmux-mcp | 2.2.0 | stdio |
How to connect Email Inbox API + Sending by Sendmux
Email Inbox API + Sending by Sendmux is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.sendmux.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: sendmux-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y sendmux-mcp@1.0.0.
It can also run locally from a Python package published to PyPI: sendmux-mcp version 2.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx sendmux-mcp. It reads these environment variables: SENDMUX_MCP_SURFACES (required), SENDMUX_MAILBOX_API_KEY (required, secret), SENDMUX_MANAGEMENT_API_KEY (required, secret) and SENDMUX_SENDING_API_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"sendmux-mcp": {
"command": "npx",
"args": [
"-y",
"sendmux-mcp@1.0.0"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Email Finder APIFind email addresses from name and company domain. x402 paid. | Remote · SSE |
| Email Finder ServerExtract emails and phones from any website via Apify. | Remote · HTTP |
| Email Footer Law LintFourteen checks on an HTML email footer: CAN-SPAM postal address and 10-business-day opt-out, CASL's. | Local · stdio |
| Email Guard MCPEmail safety for AI agents: scan inbound for prompt-injection/phishing + outbound for secret leaks. | Local · stdio |
| Email MCPIMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. | Local · stdio |
| Email MCPUnified email MCP server for Gmail, Outlook, iCloud, and IMAP with batch operations. | Local · stdio |
| Email OutreachGoal-directed email outreach: research, draft, send, triage replies. Real data, never fabricated. | Remote · HTTP |
| Email Send APISend emails programmatically via Resend. Text and HTML. x402 micropayment. | Remote · SSE |