Email Inbox API + Sending by Sendmux MCP Server
io.github.Sendmux/sendmux-mcp
AI-powered email inbox and sending with attachments, search, live events, and webhooks.
What this kind of tool is for
- Draft, send, or triage messages and email from inside your agent.
- Pipe notifications from a build or alert into your team channel automatically.
- Summarize a busy channel thread into the handful of points that matter.
How to compare servers like this
- Channel coverage:
- Check the specific app (email, chat, notifications) and whether it reads as well as writes.
- Scope of access:
- Messages are sensitive; review what the tool can see before connecting an account.
- Rate behavior:
- Bulk-sending tools should respect provider limits — avoid anything that floods.
- Maintenance signal:
- APIs in this space change often; recent updates are a strong signal.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the Email Inbox API + Sending by Sendmux MCP server?
The Sendmux MCP server provides AI agents with email inbox management and sending capabilities through the Sendmux Mailbox and Sending APIs. It enables reading, searching, and monitoring emails with attachment support, as well as composing and sending messages with files.
Sendmux MCP exposes email operations for AI agents: receive and search messages, handle attachments with download URLs, stream live mailbox events, and send emails with files. Use it to build AI workflows that interact with email inboxes, automate message handling, or integrate email into agent-driven applications.
How to install Email Inbox API + Sending by Sendmux
Copy-paste configuration for popular MCP clients.
SENDMUX_MCP_SURFACESrequiredTool surfaces to run locally.
SENDMUX_MAILBOX_API_KEYrequiredsecretMailbox API key for Mailbox API and Sending API tools.
SENDMUX_MANAGEMENT_API_KEYrequiredsecretRoot API key for Management API tools.
SENDMUX_SENDING_API_KEYsecretOptional send-capable smx_mbx_ key or owner-approved smx_agent_ token for Sending API tools when it differs from the Mailbox API key.
{
"mcpServers": {
"sendmux-mcp": {
"command": "uvx",
"args": [
"sendmux-mcp"
],
"env": {
"SENDMUX_MCP_SURFACES": "<YOUR_SENDMUX_MCP_SURFACES>",
"SENDMUX_MAILBOX_API_KEY": "<YOUR_SENDMUX_MAILBOX_API_KEY>",
"SENDMUX_MANAGEMENT_API_KEY": "<YOUR_SENDMUX_MANAGEMENT_API_KEY>",
"SENDMUX_SENDING_API_KEY": "<YOUR_SENDMUX_SENDING_API_KEY>"
}
}
}
}Tools & capabilities
Tools this server exposes to the agent.
mailbox_get_message— Retrieve a single message from the mailbox with metadata and attachment information.mailbox_list_messages— List and search messages in the mailbox with filtering and pagination.mailbox_get_attachment— Fetch attachment metadata and download URLs for message attachments.mailbox_upload_attachment— Upload files to attach to outbound messages.mailbox_send_message— Send an email message with optional attachments from the mailbox.mailbox_wait_for_message— Wait for and receive new messages with a bounded timeout.mailbox_stream_events— Stream live mailbox events in real-time (new messages, reads, etc.).sending_send_email— Send an email via the Sending API with support for attachments and templates.
Use cases
- Monitor and respond to incoming emails in real-time using live mailbox events and agent workflows.
- Search and retrieve specific messages from an inbox to extract information or trigger actions.
- Send automated emails with attachments (PDFs, reports, files) from AI agent workflows.
- Build email-based notification systems that attach files and respond to inbox changes.
- Integrate email as a communication channel for multi-step AI agent processes.
Email Inbox API + Sending by Sendmux MCP server FAQ
It's an MCP server that gives AI agents access to email inbox operations (read, search, stream events) and sending capabilities (compose, send with attachments) via the Sendmux Mailbox and Sending APIs.
Sendmux offers both free and paid tiers. Check sendmux.ai/docs for pricing and free-tier limits.
Install via PyPI: `pip install sendmux-mcp`, then configure with your Sendmux API key (smx_mbx_* or smx_agent_*). Alternatively, connect to the hosted MCP endpoint at https://mcp.sendmux.ai/mcp using OAuth.
You need a Sendmux API key: use `smx_mbx_*` keys for mailbox and sending, or owner-approved `smx_agent_*` tokens. The hosted MCP endpoint uses OAuth and does not require manual key setup.
Yes. Use `mailbox_upload_attachment` to upload files, then include them in `mailbox_send_message` or `sending_send_email`. The Sending API supports up to 10 attachments and 25 MB request body.
Yes. Use `mailbox_wait_for_message` for bounded waits or `mailbox_stream_events` to stream live mailbox events (new messages, reads, etc.) in real-time.
README (reference)
Source of truth, from the repository.
Sendmux SDKs
Official SDK, CLI, and MCP workspace for Sendmux.
- Product documentation: 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
- MCP guide: sendmux.ai/docs/guides/mcp
Packages
| Ecosystem | Package | Surface | API key or auth | Install | Source |
|---|---|---|---|---|---|
| npm | @sendmux/core | Shared TypeScript helpers | n/a | npm install @sendmux/core | packages/ts/core |
| npm | @sendmux/sending | Sending API | smx_mbx_* or owner-approved smx_agent_* | npm install @sendmux/sending | packages/ts/sending |
| npm | @sendmux/mailbox | Mailbox API | smx_mbx_* or smx_agent_* | npm install @sendmux/mailbox | packages/ts/mailbox |
| npm | @sendmux/management | Management API | smx_root_* | npm install @sendmux/management | packages/ts/management |
| npm | @sendmux/sdk | TypeScript umbrella package | surface-specific | npm install @sendmux/sdk | packages/ts/sdk |
| npm | @sendmux/cli | sendmux CLI | command/profile-specific | npm install -g @sendmux/cli | packages/ts/cli |
| npm | @sendmux/ai-sdk | Vercel AI SDK tools (agent inbox + sending) | send + receive smx_mbx_* or smx_agent_* | npm install @sendmux/ai-sdk | packages/ts/ai-sdk |
| Homebrew | sendmux | sendmux CLI | command/profile-specific | brew install sendmux/tap/sendmux | Sendmux/homebrew-tap |
| PyPI | sendmux-core | Shared Python helpers | n/a | pip install sendmux-core | packages/python/core |
| PyPI | sendmux-sending | Sending API | smx_mbx_* or owner-approved smx_agent_* | pip install sendmux-sending | packages/python/sending |
| PyPI | sendmux-mailbox | Mailbox API | smx_mbx_* or smx_agent_* | pip install sendmux-mailbox | packages/python/mailbox |
| PyPI | sendmux-management | Management API | smx_root_* | pip install sendmux-management | packages/python/management |
| PyPI | sendmux-sdk | Python umbrella package | surface-specific | pip install sendmux-sdk | packages/python/sdk |
| PyPI | sendmux-mcp | Local MCP plus hosted MCP and A2A servers | OAuth for hosted; surface-specific keys for local | pip install sendmux-mcp | packages/python/mcp |
| PyPI | langchain-sendmux | LangChain toolkit (agent inbox + sending) | send + receive smx_mbx_* or smx_agent_* | pip install langchain-sendmux | packages/python/langchain |
| Go | sendmux.ai/go/core | Shared Go helpers | n/a | go get sendmux.ai/go@v1.0.0 | go/core |
| Go | sendmux.ai/go/sending | Sending API | smx_mbx_* or owner-approved smx_agent_* | go get sendmux.ai/go@v1.0.0 | go/sending |
| Go | sendmux.ai/go/mailbox | Mailbox API | smx_mbx_* or smx_agent_* | go get sendmux.ai/go@v1.0.0 | go/mailbox |
| Go | sendmux.ai/go/management | Management API | smx_root_* | go get sendmux.ai/go@v1.0.0 | go/management |
| Go | sendmux.ai/go/sdk | Go umbrella package | surface-specific | go get sendmux.ai/go@v1.0.0 | go/sdk |
| crates.io | sendmux | Rust umbrella crate | surface-specific | cargo add sendmux | rust |
| Packagist | sendmux/core | Shared PHP helpers | n/a | composer require sendmux/core:^1.0 | packages/php/core |
| Packagist | sendmux/sending | Sending API | smx_mbx_* or owner-approved smx_agent_* | composer require sendmux/sending:^1.0 | packages/php/sending |
| Packagist | sendmux/mailbox | Mailbox API | smx_mbx_* or smx_agent_* | composer require sendmux/mailbox:^1.0 | packages/php/mailbox |
| Packagist | sendmux/management | Management API | smx_root_* | composer require sendmux/management:^1.0 | packages/php/management |
| Packagist | sendmux/sdk | PHP umbrella package | surface-specific | composer require sendmux/sdk:^1.0 | packages/php/sdk |
| RubyGems | sendmux-core | Shared Ruby helpers | n/a | gem install sendmux-core | packages/ruby/core |
| RubyGems | sendmux-sending | Sending API | smx_mbx_* or owner-approved smx_agent_* | gem install sendmux-sending | packages/ruby/sending |
| RubyGems | sendmux-mailbox | Mailbox API | smx_mbx_* or smx_agent_* | gem install sendmux-mailbox | packages/ruby/mailbox |
| RubyGems | sendmux-management | Management API | smx_root_* | gem install sendmux-management | packages/ruby/management |
| RubyGems | sendmux-sdk | Ruby umbrella package | surface-specific | gem install sendmux-sdk | packages/ruby/sdk |
Quick start
Install only the package for the surface you need.
npm install @sendmux/sending
pip install sendmux-sending
go get sendmux.ai/go@v1.0.0
cargo add sendmux
composer require sendmux/sending:^1.0
gem install sendmux-sending
Use send-capable smx_mbx_* keys or owner-approved Sending-resource smx_agent_* tokens for Sending clients. Use smx_mbx_* keys or scoped smx_agent_* tokens for Mailbox clients. Use root smx_root_* keys for Management clients. Agent tokens remain limited by server-side scopes; pre-claim self-registered agent tokens do not include email.send.
For command-line access, install the CLI:
brew install sendmux/tap/sendmux
npm install -g @sendmux/cli
sendmux --help
For MCP clients, install sendmux-mcp or connect to the hosted MCP endpoint:
pip install sendmux-mcp
sendmux-mcp-mailbox --help
The hosted MCP endpoint is https://mcp.sendmux.ai/mcp. Local MCP commands support stdio and HTTP transports; hosted MCP uses OAuth and does not require manual API keys or custom OAuth endpoints.
For A2A 1.0 clients, discover the hosted HTTP+JSON service from https://a2a.sendmux.ai/.well-known/agent-card.json. It exposes the same curated mailbox, management, and sending operations with an OAuth grant bound specifically to https://a2a.sendmux.ai/a2a/v1.
For AI-agent frameworks, first-party tool wrappers are available:
npm install @sendmux/ai-sdk ai zod # Vercel AI SDK: sendmux({ apiKey }) returns a ToolSet
pip install langchain-sendmux # LangChain: SendmuxToolkit(api_key=...).get_tools()
Both wrap the generated Sending and Mailbox clients, so the OpenAPI spec stays the single source of truth.
Attachments And Live Mailbox Events
Mailbox attachment metadata now includes a short-lived download_url. Fetch that URL promptly with a plain HTTP client; it does not require an Authorization header, but it expires after a short TTL. If a download URL expires, re-fetch the message or attachment metadata to receive a fresh URL.
For outbound files, avoid manually placing base64 in prompts or source strings. Use the zero-context path for your lane:
- CLI:
sendmux mailbox:send-message --attach ./report.pdforsendmux sending:send --attach ./report.pdf. - TypeScript: use
@sendmux/mailbox/nodesendMailboxMessageWithFiles(...)or@sendmux/sending/nodesendEmailWithFiles(...). - Python: use
sendmux_mailbox.send_mailbox_message_with_files(...)orsendmux_sending.send_email_with_files(...). - MCP: local stdio can use
mailbox_upload_attachmentwithfile_path; hosted and shell-capable agents can mint a presigned upload URL,PUTbytes to it without an API key, then send with the returnedblob_id.
Mailbox direct uploads, presigned uploads, CLI --attach, and mailbox SDK file helpers share the mailbox attachment cap: currently 7,500,000 bytes per attachment. Sending API attachment helpers encode files into the send request body; the generated Sending API limit is max 10 attachments and a 25 MB request body.
Small generated attachments can still use inline base64 where the API schema supports them. MCP inline base64 is capped at 32 KiB decoded; the cheaper alternatives are file_path, presigned upload, CLI --attach, and SDK file helpers.
Live mailbox events are available through idiomatic lanes:
- TypeScript:
streamMailboxEvents(...)returns an async iterator over typed mailbox realtime events. - Python:
iter_mailbox_events(...)yields typedMailboxRealtimeEventmodels from the generated mailbox client. - CLI:
sendmux mailbox:stream-events --followprints one JSON event per line until the stream closes or the process is interrupted. - MCP: use
mailbox_wait_for_messagefor bounded waits inside agent tool calls, thenmailbox_get_attachmentto renew attachment metadata and fetchdownload_url.
Repository structure
| Path | Purpose |
|---|---|
packages/ts | TypeScript SDK packages and the sendmux CLI. |
packages/python | Python SDK packages and the sendmux-mcp package. |
go | Go module sendmux.ai/go and subpackages. |
rust | Rust crate published as sendmux on crates.io. |
packages/php | PHP package sources used for Packagist packages and public split repositories. |
packages/ruby | RubyGem package sources. |
codegen | Generator configuration and templates. |
scripts | Generation, verification, publishing, and release helper scripts. |
docs | Surface-coverage and live E2E audit artefacts. |
.github/workflows | CI, canary, live E2E, and release workflows. |
Versioning and support
SDK packages track the Sendmux public API contracts. Patch versions can differ between packages when a fix only affects one ecosystem or runtime.
Generated clients are built from committed OpenAPI snapshots. Any API contract change must update the snapshots and generated output in the same change.
For help, open a GitHub issue with the package name, version, command or import path, and the request ID from any API error response.
Contributing
Open pull requests against this repository. Keep generated output, source snapshots, and verification artefacts together in the same change.
Security issues should be reported through GitHub Security Advisories.
Licence
This repository is available under the MIT licence.
Related MCP servers
Thrd MCP: agent email tools for events/threads, safe send/reply, usage, trust and security.
View repository →
Zammad MCP
Zammad ticket, article, and Knowledge Base operations via CLI and MCP server for AI agents

io.github.Shreyas-Profile/telegram-mcp
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
ChatGenius tools: Instagram, Facebook, WhatsApp and SMS inbox, contacts, bookings, flows, posts.
Pay-per-use web extract, token prices, and wallet balances via x402 USDC micropayments.
View repository →SomaCheck returns proposition-specific Aligned or Unaligned plus model confidence.

