Source: https://qbash.com/docs/clients/claude-code # How to add a remote MCP server to Claude Code To add a remote MCP server to Claude Code, run `claude mcp add --transport http `, then run `/mcp` inside Claude Code to sign in. Claude Code can reach qbash in two ways. Pick one, because a server added with `claude mcp add` at the same URL hides the claude.ai connector. - **Add it with a command**, as below. - **Use your claude.ai connector.** If you [added qbash on claude.ai](https://qbash.com/docs-markdown/clients/claude.md) and sign in to Claude Code with the same Claude subscription, it is already there. `/mcp` lists it as coming from claude.ai. Claude Code skips claude.ai connectors when it runs on an API key or a cloud provider such as Amazon Bedrock. :::note[Here from Google? Hi, we make the server in the screenshots] - Claude Code can build a qbash Task from a spec and deploy it, call your connected accounts, and read the knowledge bases your team keeps in memory folders. - You don't need qbash to follow this guide. Any remote MCP server goes in the same command. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## Add it with a command ```bash claude mcp add --transport http qbash https://mcp.qbash.com/mcp ``` Then start Claude Code, run `/mcp`, select qbash and sign in to qbash in the browser. `claude mcp login qbash` runs the same sign-in from the shell. ## Choose who gets it `--scope` decides where the server is saved: | Scope | Who gets it | Saved in | |---|---|---| | `local` (default) | You, in the current project only | `~/.claude.json`, under that project | | `user` | You, in every project | `~/.claude.json` | | `project` | Everyone who works in the project | `.mcp.json` in the project root, committed with the code | To have qbash in every project: ```bash claude mcp add --transport http --scope user qbash https://mcp.qbash.com/mcp ``` A `project` server is shared as configuration only. Claude Code asks each person to approve it, and each person signs in to qbash with their own account. ## Without a browser On a machine with no browser, `claude mcp login qbash --no-browser` prints the sign-in URL. Open it on any device, sign in, then paste the address the browser ends up on back into the terminal. You can also create a qbash [access token](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md#connect) and pass it as a header: ```bash claude mcp add --transport http qbash https://mcp.qbash.com/mcp \ --header "Authorization: Bearer " ``` Keep `--header` after the URL. It accepts several values, so before the name it would read the name as a second header. Keep token servers out of the `project` scope, since `.mcp.json` is committed to the repository. Anthropic's [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp) covers the other options. ## If your organization manages Claude Code Anyone can run `claude mcp add` unless the organization deploys managed settings. If the command fails with "enterprise MCP configuration is active and has exclusive control", ask your admin to allow qbash's URL. The controls are: | Setting | Effect | |---|---| | `managed-mcp.json` | Only the servers in this file load, and `claude mcp add` stops working | | `allowedMcpServers` and `deniedMcpServers` | Allow or block servers by URL, command or name. A deny always wins | | `allowManagedMcpServersOnly` | Users can't widen the allowlist from their own settings | | `managedMcpServers` | Adds remote servers for every user | A claude.ai connector that the organization added shows up in Claude Code for people signed in with a Claude subscription, with the organization's tool policies applied. Sources: Anthropic's [Claude Code MCP docs](https://code.claude.com/docs/en/mcp) and [managed MCP configuration](https://code.claude.com/docs/en/managed-mcp), checked 2026-11-04.