MCP Server

Connect Solari to Claude, Cursor, Windsurf or any other MCP client and your agent gets a real browser it can drive, plus sandboxes and GUI desktops it can run code in. No wrapper code to write.

The Solari MCP server exposes 37 tools over the Model Context Protocol. There are two ways to connect: a hosted endpoint (no install, works everywhere including Claude on web and mobile) or a local server via npx.

Hosted connector

Point your client at our endpoint and authenticate with your Solari API key. Nothing to install or keep running.

https://mcp.getsolari.com/mcp

Claude

In Claude, open Settings → Connectors → Add custom connector and paste the URL above. On the authentication step, the exact field names depend on your connector dialog, but the settings you need are:

1. Set Authentication to No sign-in. Solari authenticates with a static API key, not OAuth — leaving this on "Sign in now" or "Sign in when needed" reserves the Authorization header for OAuth and hides it from the list below.
2. Open Request headers, choose authorization from the header-name list, and enter Bearer slr_live_… as the value — including the literal word "Bearer" and the space. Claude sends whatever you type verbatim; it does not add the scheme for you.

If your organization is on Team or Enterprise, note that the connector URL (and any header) is set once by an Owner for everyone — a default configured this way is an organization default, not a per-person one. Use profileId per call if you need it to vary by person.

An Owner's org-wide header and your own query parameter can disagree, and the header will still win — but you'll be able to tell. When a session starts signed in via a configured default (not an explicit profileId), the response from solari_browser_create will include defaultOrigin: "header" | "query" | "env" alongside profileSource, naming which source actually won. If you expected your own query parameter and the response says defaultOrigin: "header", that will mean the org default overrode you, not a bug.

Connectors are shared across Chat, Code and Cowork, so you only add it once.

Prefer configuration as a file? Claude Desktop and Claude Code both read this shape:

{
  "mcpServers": {
    "solari": {
      "type": "http",
      "url": "https://mcp.getsolari.com/mcp",
      "headers": { "Authorization": "Bearer slr_live_…" }
    }
  }
}

Local server via npx

Runs on your machine and talks to Solari over the network. Requires Node 18 or newer.

{
  "mcpServers": {
    "solari": {
      "command": "npx",
      "args": ["-y", "@solarisdk/mcp"],
      "env": { "SOLARI_API_KEY": "slr_live_…" }
    }
  }
}

For Claude Desktop that file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (%APPDATA%\Claude\ on Windows) — or use Developer → Edit Config. Quit and reopen the app afterwards; configuration is read at startup.

Set a default profile (local server)

Set SOLARI_DEFAULT_PROFILE to a saved profile's name (an id also works, but the name is what you already see in the console) and every solari_browser_create call that omits profileId starts signed in with it — your agent stops asking which profile to use. An explicit profileId on a call always overrides the default; omit both to get a fresh browser with no profile, same as before.

{
  "mcpServers": {
    "solari": {
      "command": "npx",
      "args": ["-y", "@solarisdk/mcp"],
      "env": {
        "SOLARI_API_KEY": "slr_live_…",
        "SOLARI_DEFAULT_PROFILE": "work"
      }
    }
  }
}

solari_browser_create's response echoes profileId and profileSource ("explicit" or "default") whenever a profile is in play, so you can tell from the transcript whether the default put you in automatically. If the configured value doesn't match any saved profile by name or id, the call fails with an error naming what it couldn't find, rather than silently starting signed out.

Get an API key

Create one from the API Keys tab at console.getsolari.com. The same slr_live_… key works for browsers, sandboxes and desktops. You'll see it once, so copy it then.

Check it worked

Ask your agent to do something that needs a browser. It should call solari_browser_create first, then navigate.

Open example.com in a Solari browser and tell me the page heading.

In Claude, the tools appear under the tool (hammer) icon once the connector is loaded.

Tools

Browser

A Solari cloud browser session, driven over CDP. Start with solari_browser_create; it returns a sessionId the other tools take.

Sandboxes and desktops

solari_sandbox_create gives you a headless microVM; solari_desktop_create gives you a GUI one and returns a streamUrl you can watch over noVNC. The GUI tools (screenshot, click, type, open) require a desktop.

Sessions and cost

Every *_create call starts a billable session, exactly as it would through the SDK — see Plans & Pricing. Two things worth knowing:

• Browser sessions are released when the agent calls solari_browser_close, and the server also releases anything still open when a conversation goes idle or it shuts down.
• Sandboxes and desktops idle-pause rather than being destroyed, so their state survives; solari_connect re-attaches and resumes. Use solari_kill when you're done with one.

Your plan's concurrency limits apply, so an agent that opens sessions without closing them will eventually see a concurrency error.

Environment variables

For the local server: