Blueprint MCP Server

Blueprint MCP monorepo - MCP server and browser extensions

Local serverstdioTypeScript

What is the Blueprint MCP MCP server?

Blueprint MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Blueprint MCP monorepo - MCP server and browser extensions.

What you get

An MCP (Model Context Protocol) server that lets AI assistants control your actual browser (Chrome, Firefox, or Opera) through a browser extension. Unlike headless automation tools, this uses your real browser profile with all your logged-in sessions, cookies, and extensions intact.

Setting it up

The server ships on npm as @railsblueprint/blueprint-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

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

  • Navigation — The Navigation tool exposed by this server
  • Interaction — The Interaction tool exposed by this server
  • Advanced — The Advanced tool exposed by this server
  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The Setup tool exposed by this server
  • Testing — The Testing tool exposed by this server

Configuration and credentials

You will need one environment variable: AUTH_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 18+ - A supported browser (Chrome, Firefox, Edge, or Opera) - npm or yarn

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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the blueprint mcp mcp server does with a few real requests.

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. Blueprint MCP's toolset — Navigation, Interaction, Advanced and 3 more — is a fair guide to whether it matches your workflow. It is maintained by railsblueprint; 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.

Available tools

ToolWhat it does
NavigationThe Navigation tool exposed by this server.
InteractionThe Interaction tool exposed by this server.
AdvancedThe Advanced tool exposed by this server.
PrerequisitesThe Prerequisites tool exposed by this server.
SetupThe Setup tool exposed by this server.
TestingThe Testing tool exposed by this server.

How to install the Blueprint MCP MCP server

{
  "mcpServers": {
    "blueprint": {
      "command": "npx",
      "args": ["-y", "@railsblueprint/blueprint-mcp"],
      "env": {
        "AUTH_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18+ - A supported browser (Chrome, Firefox, Edge, or Opera) - npm or yarn
VariableDescriptionRequired
AUTH_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Blueprint MCP to Navigation.
  • Use Blueprint MCP to Interaction.
  • Use Blueprint MCP to Advanced.

Frequently asked questions

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