Chromewright MCP Server

Chromewright is a local-first browser automation MCP server built on Chrome DevTools Protocol (CDP). It exposes a real Chrome or Chromium browser to

Remote serverstreamable-http

What is the Chromewright MCP server?

Chromewright is a local-first browser automation MCP server built on Chrome DevTools Protocol (CDP). It exposes a real Chrome or Chromium browser to MCP clients over stdio or loopback streamable HTTP, with high-level tools for navigation. Exposed over MCP by the chromewright mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • Prerequisites — The Prerequisites tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

  • chromewright on your PATH - Chrome, Chromium, or another CDP-compatible browser - An MCP client that supports streamable HTTP or stdio servers

When to reach for it

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. Chromewright's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by bnomei; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the chromewright mcp server does with a few real requests.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the Chromewright MCP server

{
  "mcpServers": {
    "chromewright": {
      "transport": "streamable_http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

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

Configuration

  • chromewright on your PATH - Chrome, Chromium, or another CDP-compatible browser - An MCP client that supports streamable HTTP or stdio servers

Example prompts to try

  • Use Chromewright to Prerequisites.

Frequently asked questions

It connects Chromewright to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Chromewright directly.