Source: https://qbash.com/docs/clients/cursor # How to add a remote MCP server to Cursor To add a remote MCP server to Cursor, add its URL under `mcpServers` in `~/.cursor/mcp.json`, or open an install link, then sign in when Cursor asks. The `mcp.json` file in your home folder applies to every project, and one inside a project applies to that project only. :::note[Here from Google? Hi, we make the server in the screenshots] - qbash runs Tasks, which are Python programs with AI steps, on its own servers, alongside your connected accounts and shared memory folders. Cursor's agent can call all of it as tools. - You don't need qbash to follow this guide. Any remote MCP server goes in the same `mcp.json`. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## With the install link [Add qbash to Cursor](https://qbash.com/docs/clients/cursor:/anysphere.cursor-deeplink/mcp/install?name=qbash&config=eyJ1cmwiOiJodHRwczovL21jcC5xYmFzaC5jb20vbWNwIn0=) Cursor opens and asks you to install the server. Confirm it, then sign in to qbash when Cursor asks you to authenticate, and pick the qbash organization Cursor should use. ## In mcp.json Add qbash to `~/.cursor/mcp.json` for every project, or to `.cursor/mcp.json` in a project's root for that project only: ```json { "mcpServers": { "qbash": { "url": "https://mcp.qbash.com/mcp" } } } ``` Open **Customize** in Cursor's sidebar, check that the qbash toggle is on, and complete the qbash sign-in when Cursor asks you to authenticate. If qbash doesn't appear, restart Cursor. ## With an access token To skip the browser sign-in, create a qbash [access token](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md#connect) and send it as a header. Cursor can read it from an environment variable, which keeps the token out of the file: ```json { "mcpServers": { "qbash": { "url": "https://mcp.qbash.com/mcp", "headers": { "Authorization": "Bearer ${env:QBASH_TOKEN}" } } } } ``` Keep tokens out of a project's `.cursor/mcp.json` if the project is committed to a shared repository. Cursor's [MCP documentation](https://cursor.com/docs/mcp) covers the other settings. ## If your team manages Cursor Free, Pro and Teams plans can add any remote server. On Teams, admins can also share servers with the team under **Plugins & MCPs** in the dashboard. On Enterprise, an admin can set an MCP allowlist under **MCP Configuration** in the team dashboard, or push one to `~/.cursor/permissions.json` with device management. Any server that doesn't match the allowlist is blocked, so ask your admin to add `https://mcp.qbash.com/*`. Sources: Cursor's [MCP docs](https://cursor.com/docs/context/mcp) and [model and integration management](https://cursor.com/docs/enterprise/model-and-integration-management), checked 2026-11-04.