Source: https://qbash.com/docs/clients/other # How to connect any MCP client to a remote MCP server Any client that supports remote MCP servers can connect with a URL and a sign-in. 1. Add a remote MCP server in the client. If it asks for a transport, choose **Streamable HTTP**. 2. Enter `https://mcp.qbash.com/mcp` as the URL. 3. Choose OAuth when the client asks how to authenticate, then sign in to qbash and pick an organization. qbash publishes its OAuth settings on the server, so a client that discovers them needs no client ID or secret from you. :::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. Your client can call all of it as tools. - You don't need qbash to follow this guide. Any remote MCP server goes in the same setting. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## With an access token If the client can't sign in through a browser, create an [access token](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md#connect) in qbash and send it with every request: ``` Authorization: Bearer ``` A client that only runs local servers over standard input can't reach qbash directly.