Circuit MCP Server

Snowfort Circuit MCP - Computer use for webapps and electron apps

Local serverstdioTypeScript

What is the Circuit MCP MCP server?

Circuit MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Circuit MCP directly instead of describing what you should do. Snowfort Circuit MCP - Computer use for webapps and electron apps.

What you get

Circuit MCP is a comprehensive Model Context Protocol (MCP) server suite that enables AI coding agents to automate both web browsers and Electron desktop applications with unparalleled precision and flexibility.

What the assistant can call

Once Circuit MCP is connected, these are the calls the assistant has available:

  • Cross — Browser Support**: Chromium, Firefox, WebKit
  • Navigation — History control, page reload, URL navigation
  • Multi — Window Management**: Control multiple app windows simultaneously
  • Accessibility-First — Built-in accessibility tree navigation with element refs
  • browser_launch — Launch browser with AI optimizations
  • browser_navigate — Navigate to URL (includes auto-snapshot)
  • browser_resize — Resize browser viewport
  • browser_handle_dialog — Set dialog auto-response
  • browser_tab_new — Create new browser tab
  • browser_tab_list — List all open tabs
  • browser_tab_select — Switch to specific tab
  • browser_tab_close — Close specific tab

Setting it up

@snowfort/circuit-web on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Circuit MCP's toolset — Cross, Navigation, Multi and 11 more — is a fair guide to whether it matches your workflow. It is maintained by snowfort-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Circuit MCP.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the circuit mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
CrossBrowser Support**: Chromium, Firefox, WebKit
NavigationHistory control, page reload, URL navigation
MultiWindow Management**: Control multiple app windows simultaneously
Accessibility-FirstBuilt-in accessibility tree navigation with element refs
browser_launchLaunch browser with AI optimizations
browser_navigateNavigate to URL (includes auto-snapshot)
browser_resizeResize browser viewport
browser_handle_dialogSet dialog auto-response
browser_tab_newCreate new browser tab
browser_tab_listList all open tabs
browser_tab_selectSwitch to specific tab
browser_tab_closeClose specific tab
browser_network_requestsGet network request history
browser_console_messagesGet console message history

How to install the Circuit MCP MCP server

{
  "mcpServers": {
    "circuit-web": {
      "command": "npx",
      "args": ["@snowfort/circuit-web@latest"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Circuit MCP to Cross.
  • Use Circuit MCP to Navigation.
  • Use Circuit MCP to Multi.

Frequently asked questions

It connects Circuit MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Cross, Navigation, Multi, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Circuit MCP directly.