> ## Documentation Index
> Fetch the complete documentation index at: https://sendmux.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP client setup

> Configure Qubrics MCP in documented AI clients.

Use this page to connect Qubrics 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.

> [!WARNING]
>
> Replace placeholder keys and tokens before running any snippet. Do not commit
> `smx_root_`, `smx_mbx_`, or private HTTP bearer tokens to version control.

> [!NOTE]
>
> This page connects live Qubrics MCP tools. To install the Qubrics skills or
> plugin marketplace first, use [Agent skills](https://sendmux.ai/docs/ai-integrations/agent-skills.md).

## Choose a setup

> [card] [Hosted OAuth](#hosted-oauth-clients)
>
> Use this for Atlassian, Claude, Cursor, Codex, Gemini CLI, Qwen Code, Kiro, OpenCode, Zed, Visual Studio, Hoot, and ChatGPT.

> [card] [Local stdio](#local-stdio-clients)
>
> Use this when your client can launch `sendmux-mcp` on your machine.

> [card] [Private HTTP](#private-http-clients)
>
> Use this when your client needs a URL or runs outside your laptop.

> [accordion] Compatibility matrix
>
> These labels describe documented configurations. They do not claim automatic client certification unless a row says so.
>
> | Client | Recommended setup | Connection and validation |
> | - | - | - |
> | Atlassian | Hosted OAuth | Custom external MCP server; documented, manual acceptance pending |
> | Claude and Claude Desktop | Hosted OAuth | Custom connector; documented |
> | Claude Code | Hosted OAuth | Remote HTTP, local stdio, private HTTP; documented |
> | Cursor | Hosted OAuth | Remote HTTP, local stdio, private HTTP; documented |
> | Codex | Hosted OAuth | Remote HTTP, local stdio, private HTTP; documented |
> | ChatGPT | Hosted OAuth app | Remote HTTPS MCP app |
> | Hoot | Hosted OAuth | Remote HTTP |
> | Gemini CLI | Hosted OAuth | Remote HTTP, local stdio, private HTTP |
> | Qwen Code | Hosted OAuth | Remote HTTP, local stdio, private HTTP |
> | Kiro | Hosted OAuth | Remote HTTP, local stdio, private HTTP |
> | OpenCode | Hosted OAuth | Remote MCP, local MCP |
> | Zed | Hosted OAuth | Remote OAuth, local command, private HTTP |
> | Visual Studio | Hosted OAuth | Remote HTTP, local stdio |
> | VS Code | Local stdio or private HTTP | Local stdio, private HTTP |
> | Windsurf and Cascade | Local stdio or private HTTP | Local stdio, private HTTP |
> | Cline | Local stdio or private HTTP | Local stdio, private HTTP |
> | Roo Code | Local stdio or private HTTP | Local stdio, private HTTP |
> | Warp local app | Local stdio or private HTTP | Local command, URL server |
> | JetBrains AI Assistant | Local stdio or private HTTP | Local stdio, private HTTP |
> | Continue | Local stdio or private HTTP | Local stdio, private HTTP |
> | LM Studio | Private HTTP | Remote MCP using Cursor-style JSON |
> | GitHub Copilot CLI | Local stdio or private HTTP | Local, HTTP |
> | GitHub Copilot coding agent | Private HTTP | Repository MCP config with secrets |

> [!NOTE]
>
> A client can still use Qubrics when hosted OAuth is not listed. Use local
> stdio if the client can launch commands, or private HTTP if it needs a URL.

## Hosted OAuth clients (Recommended)

Use the hosted endpoint when the client supports remote MCP OAuth:

```text theme={null}
https://mcp.qubrics.com/mcp
```

> [card] [Atlassian](https://sendmux.ai/docs/ai-integrations/mcp/clients/atlassian.md)
>
> Add Qubrics as a custom external MCP server in Atlassian administration.

## Local stdio clients

> [!WARNING]
>
> Before upgrading an existing installation, keep its working package environment,
> dependency state, and MCP client and tool configuration. Version 2.0.0 removes
> local `file_path` and roots inputs from MCP attachment tools. Before switching
> existing agents, follow the [upgrade and rollback guidance](https://github.com/qubrics/qubrics-sdk/blob/main/packages/python/mcp/README.md#200-upgrade).

Install the local package once:

```bash theme={null}
pip install --upgrade sendmux-mcp
```

Use a mailbox key for Mailbox or Sending:

```bash theme={null}
export QUBRICS_MBX_KEY=smx_mbx_...
```

Use a root key for Management:

```bash theme={null}
export QUBRICS_ROOT_KEY=smx_root_...
```

## Private HTTP clients

Start a local HTTP MCP server:

```bash theme={null}
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
```

Use `http://127.0.0.1:8765/mcp` as the client URL.

## 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 Qubrics tools appear.

**3. Select a mailbox when needed**

For a hosted multi-mailbox grant, call `qubrics_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

> [card] [MCP overview](https://sendmux.ai/docs/ai-integrations/mcp)
>
> Compare Doc Search MCP, hosted MCP, local stdio, and private HTTP.

> [card] [API keys](https://sendmux.ai/docs/account/api-keys.md)
>
> Create mailbox and root keys for local MCP.

> [card] [Agent skills](https://sendmux.ai/docs/ai-integrations/agent-skills.md)
>
> Teach AI coding agents the Qubrics workflows and efficient defaults.

> [card] [CLI](https://sendmux.ai/docs/developer-tools/cli.md)
>
> Run Qubrics workflows from your terminal.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.