Cursor
Add Scalebrowser as an MCP server in Cursor, for one project or for every project.
Cursor reads MCP servers from a JSON file: one per project, or one for everything you open.
Before you start
Everything below assumes a daemon that is already running and a token to reach it with.
The app starts the daemon for you. The token is the contents of
%LOCALAPPDATA%\Scalebrowser\token, and the address it is listening on is the
native_addr field of %LOCALAPPDATA%\Scalebrowser\runtime.json. That is usually
127.0.0.1:8787, but the app moves up a port when something else already holds it.
scalebrowser-daemon --generate-token prints a token and stores it under
<data_dir>/token. The address is whatever bind_addr says, which is 127.0.0.1:8787
unless you changed it. See Install & run.
The token is a full-power credential. It reaches every profile, every stored session and the whole management API. Treat it like a password: keep it out of a repository, and prefer your client's environment-variable syntax over a literal in a config file that gets committed.
Add the server
Two locations, same shape. .cursor/mcp.json in a project applies to that project;
~/.cursor/mcp.json in your home directory applies everywhere.
{
"mcpServers": {
"scalebrowser": {
"url": "http://127.0.0.1:8787/v1/mcp",
"headers": {
"Authorization": "Bearer ${env:SCALEBROWSER_TOKEN}"
}
}
}
}The ${env:...} form keeps the token out of the file, which matters for the project-scoped
copy, because that one sits in your repository.
Cursor picks the file up without a restart and lists the server under Settings → MCP.
What the agent can do now
Ask it to open a page and it will lease a profile, bind a tab and start reading. The tool set, the page map and the failure shapes are on MCP server; what the agent is allowed to do is decided by the daemon, not by the client, so see tool profiles.