Source: https://qbash.com/docs/clients/overview # How to add an MCP server to ChatGPT, Claude, Codex, Cursor and other AI clients ChatGPT, Codex in the ChatGPT app and dots add a remote MCP server on the Plugins page, Claude adds it under Connectors, the Codex CLI and Claude Code take a terminal command, and Cursor and VS Code read an `mcp.json` file. The table below links a step-by-step guide for each, with qbash's server as the example. Every client below connects to the same qbash server URL and signs in with your qbash account: ``` https://mcp.qbash.com/mcp ``` That is the [official MCP server](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md), which gives the client your Tasks, connectors and memory folders under your own permissions. A [custom server](https://qbash.com/docs-markdown/mcp-servers/overview.md) you build in qbash has its own URL, in the form `https://mcp.qbash.com/mcp/execution/`. Open the server under **MCP Servers** in qbash and copy it from the top of the page. Use it in place of the official URL and the steps stay the same. | Client | Where you add qbash | Who gets it | Guide | |---|---|---|---| | ChatGPT | The Plugins page, as a custom MCP server | You, or your whole workspace if an admin publishes it | [ChatGPT](https://qbash.com/docs-markdown/clients/chatgpt.md) | | dots | A chat message asking the dot to add the URL, or a ChatGPT plugin you have installed | You, inside that dot | [dots](https://qbash.com/docs-markdown/clients/chatgpt-dots.md) | | Codex | A ChatGPT plugin in the ChatGPT app, or the `codex mcp add` command or `config.toml` for the CLI and IDE extension | You, in the ChatGPT app or on that computer | [Codex](https://qbash.com/docs-markdown/clients/codex.md) | | Claude | Customize, then Connectors, on claude.ai or the desktop app | You, or your organization if an Owner adds it | [Claude](https://qbash.com/docs-markdown/clients/claude.md) | | Claude Code | The `claude mcp add` command, or a claude.ai connector | You, one project, or everyone who clones the project | [Claude Code](https://qbash.com/docs-markdown/clients/claude-code.md) | | Cursor | An install link, or `mcp.json` | You, in every project or one | [Cursor](https://qbash.com/docs-markdown/clients/cursor.md) | | VS Code | An install link, the **MCP: Add Server** command, or `mcp.json` | You, or everyone who opens the workspace | [VS Code](https://qbash.com/docs-markdown/clients/vscode.md) | | Grok Bot | A chat message asking the Bot to add the URL | You, in every Bot you run, within your team's connector policy | [Grok Bot](https://qbash.com/docs-markdown/clients/grok-bot.md) | | Muse | A chat message asking Muse to add the URL | You | [Muse](https://qbash.com/docs-markdown/clients/muse.md) | | Muse Code | `~/.config/muse/settings.json`, then `muse mcp login` | You, on that computer | [Muse Code](https://qbash.com/docs-markdown/clients/muse.md#muse-code) | | Anything else | The client's remote MCP server setting | Depends on the client | [Other clients](https://qbash.com/docs-markdown/clients/other.md) | ## Do you need an admin? | Client | Personal plans | Team plans | |---|---|---| | ChatGPT | Yes, on any plan including Free | Depends on your role. If you can't, talk to your workspace owner | | dots | Pro, through your own plugin | An admin adds the plugin, and on Enterprise and Edu turns dots on | | Claude | Yes. Free allows one custom connector | Owners add it, members connect it | | Claude Code | Yes | Yes, unless managed settings restrict MCP servers | | Codex | Yes | In the ChatGPT app, the same as ChatGPT. For the CLI, an admin allows Codex locally and may set an MCP allowlist | | Cursor | Yes | Enterprise admins may set an MCP allowlist | | VS Code with Copilot | Yes | The **MCP servers in Copilot** policy must be on | | Grok Bot | Yes | The team connector policy must allow it | | Muse and Muse Code | Yes | No admin settings | Each guide covers the settings for its client, with sources. :::note[Here from Google? Hi, we make the server in the screenshots] - qbash runs Tasks, which are Python programs with AI steps, alongside your connected accounts and shared memory folders. Each of these clients can call all of it as tools. - You don't need qbash to follow this guide. Any remote MCP server goes in the same place in each client. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## Sign-in Each client opens a qbash sign-in page the first time it connects. If you belong to more than one qbash organization, you pick the one that client uses. A custom server belongs to one organization, so its sign-in skips that choice. To see which apps are signed in, or to sign one out, open **MCP Servers** in qbash and then **Official qbash MCP server**. Coding tools can also send a qbash [access token](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md#connect) in an `Authorization` header in place of signing in. Each guide shows how.