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 27 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

Rolling out — use the local npx server if it 404s

The hosted connector is still being rolled out and may return 404 on some accounts. If your client can't reach it, use the local npx server below, which is generally available today.

Claude

In Claude, open Settings → Connectors → Add custom connector, paste the URL above, and set an Authorization header of Bearer slr_live_…. 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.

Restart, don't just close the window

Closing the Claude window leaves the app running and your connector won't load. Quit fully (⌘Q on macOS) and reopen.

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.

An MCP transcript is credential material

Your agent's conversation will contain session IDs that grant control of a running browser or desktop. Treat transcripts and logs accordingly, and rotate the key from the console if one leaks.

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.

Tool	What it does
`solari_browser_create`	Start a session. Options: `stealth`, `proxy`, `captcha`, `recording`, `profileId`
`solari_browser_navigate`	Go to a URL; returns final URL, title and status
`solari_browser_read_page`	Page text, links, or HTML
`solari_browser_screenshot`	JPEG of the current page
`solari_browser_click` / `solari_browser_type` / `solari_browser_key`	Interact by CSS selector or coordinates
`solari_browser_evaluate`	Run a JavaScript expression in the page
`solari_browser_replay_url`	Replay URL for a session created with `recording: true`
`solari_browser_close`	Release the session

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.

Tool	What it does
`solari_sandbox_create` / `solari_desktop_create`	Create a VM; returns a sessionId
`solari_exec` / `solari_run_command_bg`	Run a shell command, blocking or in the background
`solari_run_code`	Run code (Python by default), including charts
`solari_read_file` / `solari_write_file` / `solari_list_files`	Guest filesystem
`solari_get_preview_url`	Public URL for a port inside the VM (e.g. a dev server)
`solari_screenshot` / `solari_click` / `solari_type` / `solari_key` / `solari_open_app`	Control the desktop GUI
`solari_list` / `solari_connect` / `solari_kill`	List VMs, re-attach to one by id (resuming it if paused), or destroy it

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:

Variable	Default	Purpose
`SOLARI_API_KEY`	—	Required. Your API key
`SOLARI_BASE_URL`	`https://api.getsolari.com`	Sandbox and desktop API
`SOLARI_BROWSER_URL`	`SOLARI_BASE_URL`	Browser API, when it differs

Other MCP clients

Cursor, Windsurf and Claude Code use the same two configuration shapes above. In Claude Code you can add the hosted connector directly: claude mcp add --transport http solari https://mcp.getsolari.com/mcp.