Email inbox API for AI agents with MCP tools for Mailbox, Management, and Sending APIs.
If you already use Sendmux MCP, the sendmux mcp mcp server is the piece that lets your assistant work with it directly. Email inbox API for AI agents with MCP tools for Mailbox, Management, and Sending APIs.
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.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
CLI — sendmux mailbox:send-message --attach ./report.pdf or sendmux sending:send --attach ./report.pdfTypeScript — use @sendmux/mailbox/node sendMailboxMessageWithFiles(...) or @sendmux/sending/node sendEmailWithFiles(...)MCP — local stdio can use mailbox_upload_attachment with file_path; hosted and shell-capable agents can mint a presigned upload URL, PUT bytes to itEcosystem — PackageHomebrew — sendmuxPyPI — sendmux-corecrates.io — sendmuxPackagist — sendmux/coreRubyGems — sendmux-corePath — PurposePlenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sendmux MCP's toolset — CLI, TypeScript, MCP and 7 more — is a fair guide to whether it matches your workflow. It is maintained by Sendmux; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| CLI | sendmux mailbox:send-message --attach ./report.pdf or sendmux sending:send --attach ./report.pdf. |
| TypeScript | use @sendmux/mailbox/node sendMailboxMessageWithFiles(...) or @sendmux/sending/node sendEmailWithFiles(...). |
| MCP | local stdio can use mailbox_upload_attachment with file_path; hosted and shell-capable agents can mint a presigned upload URL, PUT bytes to it without an API key, then send with the returned blob_id. |
| Ecosystem | Package |
| Homebrew | sendmux |
| PyPI | sendmux-core |
| crates.io | sendmux |
| Packagist | sendmux/core |
| RubyGems | sendmux-core |
| Path | Purpose |
{
"mcpServers": {
"sendmux": {
"command": "npx",
"args": ["-y", "@sendmux/core"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.