computeruse

Connect another MCP client ​

Any MCP client that can use a remote server works, if it supports:

  • the Streamable HTTP transport, and
  • signing in with OAuth in a browser.

Steps ​

  1. Choose Copy MCP URL on the session, on the list or on its page.
  2. Add a remote (HTTP) MCP server in your client with that URL. No API key or header is needed.
  3. When the client opens a sign-in page, use the Google or GitHub account that owns the session.
  4. List the server's tools. You should see run_js.

A typical client configuration:

json
{
  "mcpServers": {
    "desktop": {
      "type": "http",
      "url": "https://sessions.computeruse.site/s-abcde/mcp"
    }
  }
}

The exact keys depend on the client.

Without a person to sign in ​

Scripts, CI and other services cannot go through a sign-in page. API tokens for them are coming and are not enabled yet; see Live, coming and planned.

Several clients, one session ​

You can add the same MCP URL to more than one client. They share one desktop. Give each agent its own tab with the tab parameter of browser_execute; see MCP endpoint and tools.

Troubleshooting ​

What you seeWhy
Sign-in succeeds, then calls answer 404The account is not the session's owner, or the session was deleted.
Calls answer 409The session is stopped. Resume it in the app.
A call answers 504 with Retry-AfterThe session was still waking. Try again.