Labsco
MCP SERVER

Blueprint MCP

by railsblueprint

Automate the browser you are already logged into, through an extension instead of a headless copy.

Browser Automation, Control & Screenshots
Summary
Your session and your fingerprint, which is the whole reason to pick it.

Headless automation loses on exactly two things: sites you are already authenticated to, and sites that recognise automated browsers. Running inside the real profile solves both, at the cost of a second moving part — the extension — and of the model acting with your live logged-in identity. The network tool goes further than most: filtering, JSONPath into large responses, and replaying a captured request with its original auth.

What it is

An MCP server that drives your real browser through a companion extension, so automation runs inside your actual profile — the sessions you are signed into, the cookies you already have, the extensions you already run. Chrome, Edge, Opera and Firefox builds exist.

What you get
  • Connection control: `enable` (the required first step), `disable`, `status`, and `auth` for the paid tier
  • Navigation and tabs: `browser_navigate`, `browser_navigate_back`, `browser_tabs` to list, create, attach to or close
  • Reading a page: `browser_snapshot` for accessible content, `browser_extract_content` as markdown, `browser_take_screenshot`, `browser_console_messages`
  • `browser_network_requests` — list with filters on `urlPattern`, `method`, `status` and `resourceType`, paginated; details with headers and bodies; JSONPath querying of large JSON responses; and replay of a captured request with its original headers and authentication
  • Interaction: `browser_interact` for a sequence of actions, plus `browser_click`, `browser_type`, `browser_hover`, `browser_select_option`, `browser_fill_form`, `browser_press_key`, `browser_drag`
  • Advanced: `browser_evaluate`, `browser_handle_dialog`, `browser_file_upload`, `browser_window`, `browser_pdf_save`, `browser_performance_metrics`
  • Testing helpers: `browser_verify_text_visible`, `browser_verify_element_visible`
  • Extension development: `browser_list_extensions`, `browser_reload_extensions`
Requirements

Two halves that have to meet. The npm package `@railsblueprint/blueprint-mcp`, run by your client via `npx`, and the browser extension from the Chrome Web Store or Firefox Add-ons. They connect over a WebSocket on port 5555 on the same machine; no account is needed for that. Node.js 18+ if you build from source. The free tier is one browser on one machine — cloud relay, multiple browser instances, shared access and auto-reconnect are the paid PRO tier.

Setup effort

One command — npm install -g @railsblueprint/blueprint-mcp