Skip to main content
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.
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 Qubrics MCP tools. To install the Qubrics skills or plugin marketplace first, use Agent skills.

Choose a setup

Hosted OAuth

Use this for Atlassian, 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.
These labels describe documented configurations. They do not claim automatic client certification unless a row says so.
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.
Use the hosted endpoint when the client supports remote MCP OAuth:

Atlassian

Add Qubrics as a custom external MCP server in Atlassian administration.

Local stdio clients

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.
Install the local package once:
Use a mailbox key for Mailbox or Sending:
Use a root key for Management:

Private HTTP clients

Start a local HTTP MCP server:
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

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 Qubrics workflows and efficient defaults.

CLI

Run Qubrics workflows from your terminal.

Claude and Claude Desktop MCP setup

Configure Qubrics MCP in Claude and Claude Desktop.

Claude Code MCP setup

Configure Qubrics MCP in Claude Code.

Cursor MCP setup

Configure Qubrics MCP in Cursor.

Codex MCP setup

Configure Qubrics MCP in Codex.

ChatGPT MCP setup

Configure Qubrics MCP in ChatGPT.

Connect Atlassian to Qubrics MCP

Add hosted Qubrics MCP as a custom external server in Atlassian administration.

Hoot MCP setup

Configure Qubrics MCP in Hoot.

Gemini CLI MCP setup

Configure Qubrics MCP in Gemini CLI.

Qwen Code MCP setup

Configure Qubrics MCP in Qwen Code.

Kiro MCP setup

Configure Qubrics MCP in Kiro.

OpenCode MCP setup

Configure Qubrics MCP in OpenCode.

Zed MCP setup

Configure Qubrics MCP in Zed.

Visual Studio MCP setup

Configure Qubrics MCP in Visual Studio.

VS Code MCP setup

Configure Qubrics MCP in VS Code.

Windsurf and Cascade MCP setup

Configure Qubrics MCP in Windsurf and Cascade.

Cline MCP setup

Configure Qubrics MCP in Cline.

Roo Code MCP setup

Configure Qubrics MCP in Roo Code.

Warp local app MCP setup

Configure Qubrics MCP in Warp local app.

JetBrains AI Assistant MCP setup

Configure Qubrics MCP in JetBrains AI Assistant.

Continue MCP setup

Configure Qubrics MCP in Continue.

LM Studio MCP setup

Configure Qubrics MCP in LM Studio.

GitHub Copilot CLI MCP setup

Configure Qubrics MCP in GitHub Copilot CLI.

GitHub Copilot coding agent MCP setup

Configure Qubrics MCP in GitHub Copilot coding agent.