Blueprint Mcp For Chrome

What is Blueprint MCP for Chrome?

Blueprint MCP for Chrome is an open-source MCP server that gives AI assistants like Claude Code direct control of your real Chrome browser. It uses CSS selectors instead of page snapshots, avoiding token limits and preserving context for complex multi-step workflows.

How to use Blueprint MCP for Chrome?

Install the server globally with npm install -g @railsblueprint/blueprint-mcp, then install the companion Chrome extension. Configure your AI client by running claude mcp add browser npx @railsblueprint/blueprint-mcp@latest. The extension auto-connects when your AI client starts the MCP server.

Key features of Blueprint MCP for Chrome

• Real browser profile and session persistence
• 20+ browser tools via MCP (click, type, navigate, screenshot, etc.)
• Stealth mode uses your real browser fingerprint
• Local WebSocket mode with zero cloud dependencies
• Open source under Apache 2.0 license
• Supports PRO Cloud Relay for remote access

Use cases of Blueprint MCP for Chrome

• Web scraping that bypasses bot detection
• Automated form filling using saved passwords
• Testing workflows with logged-in accounts
• Content extraction from authenticated sites
• Browser automation working with 2FA and CAPTCHAs

FAQ from Blueprint MCP for Chrome

What runtimes or dependencies does Blueprint MCP for Chrome require?

It requires Node.js to run the MCP server and a real Chrome browser with the Blueprint extension installed.

How does Blueprint MCP for Chrome handle data privacy?

In free local mode, all communication stays on your machine via a localhost WebSocket. There is zero telemetry, tracking, or analytics, and the server works completely offline.

What transport protocols are supported?

Free tier uses a local WebSocket on port 5555. Pro tier offers a Cloud Relay for controlling the browser from anywhere and supporting multiple AI clients.

Do I need any authentication to use Blueprint MCP for Chrome?

No account is needed for the free local tier. The Pro tier requires a subscription for Cloud Relay but no additional authentication for local use.

What are the limitations of Blueprint MCP for Chrome compared to snapshot-based tools?

It does not automatically send page snapshots with every action, which saves context tokens. Content is only fetched when explicitly requested, enabling longer, more efficient workflows without hitting response size limits.