Scalebrowser MCP server

Scalebrowser MCP

Your agent got blocked, stopped at a login, or gave up on a captcha? Scalebrowser gives each AI agent its own isolated browser with a persistent identity, running on your own machine instead of a vendor's cloud. It stays signed in, handles the captcha, types like a human, and you can take over whenever you want.

This repository connects that browser to your agent over MCP: copy-paste configurations for every client the documentation covers, a small stdio bridge, and runnable SDK examples.

Before you start

• Windows 10 or 11, 64-bit, with a real GPU. Scalebrowser is a desktop app that runs on your machine. There is no hosted mode.
• A Scalebrowser account with an active plan. The way in is a 7-day trial with one browser. A payment method is required up front. Plans and prices

Free, no account needed: scalebrowser.net/check measures how your current browser looks from the outside, and scalebrowser.net/ai-agent-check measures what your automation tool does with it. Point your agent at the second one and see what a website can tell.

Try it in five minutes

1. Sign in at scalebrowser.net, open Download, and run the installer. It installs for the current user and asks for no administrator rights. SmartScreen warns on first run: choose More info, then Run anyway.
2. Start the app and press Sign in. The app then downloads and verifies the browser engine, which has to finish before any profile can start.
3. Copy your API token from Settings, General, Connect an agent.
4. Connect your agent. For Claude Code it is one command:

claude mcp add --transport http scalebrowser http://127.0.0.1:8787/v1/mcp \
     --header "Authorization: Bearer $SCALEBROWSER_TOKEN"

1. Ask it something:

Open news.ycombinator.com in a Scalebrowser profile, read the front page, and tell me the three stories with the most comments.

The agent takes a lease, which reserves a profile and starts its browser, opens the page, reads a text map of it and answers. Then ask it to release the profile.

Connect your client

Each file below is the configuration from the official documentation, ready to copy. Replace with your API token and with your Windows user name. Where each file goes, and the two spellings that fail without an error, is in clients/README.md.

What your agent gets

The agent works from a text map of the page and addresses elements by reference. It looks at the page once, then only at what moved: 13,507 tokens where Playwright MCP needs 2.1 million.

Shortened. The full README is on GitHub.