Skip to main content
Use this page to connect Sendmux MCP to your AI client. Prefer hosted OAuth when your client supports it. Use local stdio or private HTTP when the client cannot complete hosted OAuth.
Replace placeholder keys and tokens before running any snippet. Do not commit smx_root_, smx_mbx_, or private HTTP bearer tokens to version control.
This page connects live Sendmux MCP tools. To install the Sendmux skills or plugin marketplace first, use Agent skills.

Choose a setup

Hosted OAuth

Use this for Claude, Cursor, Codex, Gemini CLI, Qwen Code, Kiro, OpenCode, Zed, Visual Studio, Hoot, and ChatGPT.

Local stdio

Use this when your client can launch sendmux-mcp on your machine.

Private HTTP

Use this when your client needs a URL or runs outside your laptop.
A client can still use Sendmux when hosted OAuth is not listed. Use local stdio if the client can launch commands, or private HTTP if it needs a URL.
Use the hosted endpoint when the client supports remote MCP OAuth:
Add a custom connector with server URL https://mcp.sendmux.ai/mcp, then connect and complete the Sendmux authorisation flow.On Team and Enterprise plans, an owner may need to add the custom connector for the organisation before members can connect it.
Use /mcp in Claude Code if the server is listed as requiring authentication.
Add this to .cursor/mcp.json for one project or ~/.cursor/mcp.json for all projects.
Cursor opens the OAuth flow when the hosted server asks for authorisation.
Add this to ~/.codex/config.toml or a trusted project .codex/config.toml.
Then authenticate:
Create a custom MCP app or connector that points to https://mcp.sendmux.ai/mcp. Developer mode or workspace app setup must be available on your plan or workspace.After ChatGPT scans the tools, complete the Sendmux authorisation prompt and test the app privately before publishing it to a workspace.
Add a server with these settings:Leave the access token, custom OAuth endpoints, headers, client ID, and custom scopes empty unless Hoot adds a dedicated field for them.
Add this to your Gemini CLI settings.json.
Then run /mcp auth sendmux inside Gemini CLI.
Add this to .qwen/settings.json for one project or ~/.qwen/settings.json for all projects.
Use /mcp auth in Qwen Code if the server needs authentication.
Add this to .kiro/settings/mcp.json for one workspace or ~/.kiro/settings/mcp.json for all workspaces.
Kiro opens the browser OAuth flow when the hosted server asks for authorisation.
Add this to opencode.json.
Authenticate when prompted, or run:
Add this to Zed settings.
Do not add an Authorization header for hosted OAuth. Zed prompts for the standard MCP OAuth flow when no header is configured.
Add a remote MCP server with this JSON shape.
Click Auth above the server in the MCP configuration file, then complete the Sendmux authorisation flow.

Local stdio clients

Install the local package once:
Use a mailbox key for Mailbox or Sending:
Use a root key for Management:
Use an input variable so the key is not stored directly in .vscode/mcp.json.
Run Codex with SENDMUX_API_KEY already set, then use env_vars so the value stays outside the config file.
Add this to ~/.codeium/windsurf/mcp_config.json.
Add this through the Cline MCP settings JSON or ~/.cline/mcp.json.
Add this to the Roo MCP settings JSON.
Add this to Gemini CLI settings.json.
Add this to .qwen/settings.json or ~/.qwen/settings.json.
Add this to .kiro/settings/mcp.json or ~/.kiro/settings/mcp.json.
Add this to opencode.json.
Add this to Zed settings.
Paste this as an MCP server JSON snippet in Settings > Agents > MCP servers.
Go to Settings > Tools > AI Assistant > Model Context Protocol (MCP) and add this JSON configuration over STDIO.
Create .continue/mcpServers/sendmux-mailbox.yaml.

Private HTTP clients

Start a local HTTP MCP server:
Use http://127.0.0.1:8765/mcp as the client URL.
Warp cloud agents should use a reachable private HTTPS endpoint, not a loopback URL on your laptop.
Use the HTTP option in the MCP settings.
Create .continue/mcpServers/sendmux-local.yaml.
LM Studio follows Cursor’s mcp.json notation. Open Program > Install > Edit mcp.json and add:
Use repository-level MCP settings with a private HTTPS endpoint that the cloud agent can reach. Store the bearer token as an Agents secret or variable whose name starts with COPILOT_MCP_.
GitHub Copilot coding agent does not support remote MCP servers that require OAuth. Do not point it at the hosted Sendmux OAuth endpoint.

Verify the connection

1

Reconnect the server

Restart or reconnect the MCP server in the client.
2

Check the tools

Open the client’s MCP server list or tool picker and confirm Sendmux tools appear.
3

Select a mailbox when needed

For a hosted multi-mailbox grant, call mailbox_list_granted_mailboxes before mailbox-specific work.
4

Check private HTTP auth

For private HTTP, confirm the client sends Authorization: Bearer local-mcp-token.

Next steps

MCP overview

Compare Doc Search MCP, hosted MCP, local stdio, and private HTTP.

API keys

Create mailbox and root keys for local MCP.

Agent skills

Teach AI coding agents the Sendmux workflows and efficient defaults.

CLI

Run Sendmux workflows from your terminal.