Skip to content
WebPilot.si
Start free

Solutions · Claude apps

Your browser in the Claude apps.

Claude Desktop connects today through the mcp-remote bridge. A claude.ai connector, which needs sign-in with OAuth, is not available yet.

Start freeRead the docs

claude_desktop_config.json

{
  "mcpServers": {
    "webpilot": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.webpilot.si/mcp",
               "--header", "Authorization:${WEBPILOT_AUTH}"],
      "env": { "WEBPILOT_AUTH": "Bearer cbu_..." }
    }
  }
}

How it works

01

Claude Desktop today

Claude Desktop starts local MCP servers from its config file. mcp-remote is a small bridge that forwards those calls to https://api.webpilot.si/mcp with your token in the Authorization header. Restart Claude Desktop after editing the file.

From then on Claude can open tabs, read pages, log in from your vault and give you a viewer link, the same as any other MCP client.

02

claude.ai on the web

Custom connectors on claude.ai sign in with OAuth rather than a bearer token. The gateway accepts tokens only, so there is no claude.ai connector yet. We will say so in the changelog when there is.

03

You stay in the loop

When a site asks for something only you can give (an SMS code, a CAPTCHA the agent cannot solve), the agent hands the step to you with a link. You see the browser live, do the step and press Done; the agent carries on.

FAQ

Questions people ask

Where do I get the token?

Sign up, then create one in the console under Settings → Tokens. It starts with cbu_ and is shown once; we keep only a hash. Put it in an environment variable (WEBPILOT_TOKEN), not in a file you commit.

Why the bridge?

Claude Desktop's config file starts local programs. mcp-remote is one: it speaks stdio to Claude Desktop and Streamable HTTP to the gateway. It runs with npx, so Node.js must be installed.

Can I use claude.ai in the browser?

Not yet. claude.ai's custom connectors need OAuth sign-in, which the gateway does not offer today. Claude Desktop, Claude Code and any client that can send a bearer token work now.

Does the browser keep my logins between sessions?

Yes. Each account has its own Chromium profile on our servers: cookies, local storage and the open tabs survive disconnects and restarts. The browser stops after 20 minutes without activity; the profile and tab list stay on disk and come back on the next request.

Does the agent see my passwords?

No. Logins, card fields and authenticator (TOTP) keys live in your vault, encrypted with AES-256-GCM. The agent names an entry (browser_login{site}) and the server types the values into the page. No API returns a stored value.

Can I watch what the agent does?

Ask the agent for a viewer link (the browser_viewer tool), or open the live view in the console. Links expire after 10 minutes and are view-only unless your settings allow taking over; the server's relay enforces that, not the page.

More solutions

Give your agent a browser that remembers.

Start with the free trial. Connect Claude Code, Cursor, Codex or your own code in a minute.

Start freeSee pricing