# MCP Browser Extension > Let Claude use the Chrome you are already logged into. An MCP server (npm @mehmoodqureshi/chrome-mcp) plus a Chrome extension, so Claude Code, Cursor and other MCP hosts can work in the Chrome you are signed into. Deny-all by default. ## Pages - [Home](https://mcp-browser-extension.vercel.app/): what it is and how to install it. - [Use Claude in your logged-in Chrome](https://mcp-browser-extension.vercel.app/logged-in-chrome): Let Claude Code, Cursor or any MCP agent work in the Chrome you are signed into. No re-login, no credentials, deny-all by default. ## Docs - [Introduction](https://mcp-browser-extension.vercel.app/docs): What chrome-mcp is, why it drives your real Chrome instead of a fresh Chromium, and where to start. - [Quickstart](https://mcp-browser-extension.vercel.app/docs/quickstart): Register the MCP server, load the extension, and pair it. Three steps, one paste. - [Agent setup](https://mcp-browser-extension.vercel.app/docs/agent-setup): The exact instructions an AI agent follows to install and verify chrome-mcp on a machine. Hand it the URL and it does the rest. - [Guides](https://mcp-browser-extension.vercel.app/docs/guides): Multi-tab batches, iframes and shadow roots, observers, snapshot diffs, role locators, auth walls and PDF printing. - **Reference** - Tools - [Tools reference](https://mcp-browser-extension.vercel.app/docs/tools): Every tool chrome-mcp exposes over MCP, with arguments and examples. Generated from the 0.9.15 catalog. - [Tabs](https://mcp-browser-extension.vercel.app/docs/tools/tabs): Open, list, focus and close tabs in the real Chrome window. - [Navigation](https://mcp-browser-extension.vercel.app/docs/tools/navigation): Move a tab between pages and wait for the page to settle. - [Interaction](https://mcp-browser-extension.vercel.app/docs/tools/interaction): Click, type, select and scroll. Target by CSS selector, snapshot ref, or role and accessible name. - [Reading](https://mcp-browser-extension.vercel.app/docs/tools/reading): Get the page back as text, markdown, HTML, an accessibility snapshot, a screenshot or a PDF. - [State and scripting](https://mcp-browser-extension.vercel.app/docs/tools/state): Cookies, storage, downloads and JavaScript evaluation. - [Observers](https://mcp-browser-extension.vercel.app/docs/tools/observers): Console output, network requests and native dialogs. Requires --enable-observers. - [Session and artifacts](https://mcp-browser-extension.vercel.app/docs/tools/session): Backend status, sign-in wall detection, and where downloads, results and screenshots are stored. - [Batch](https://mcp-browser-extension.vercel.app/docs/tools/batch): Run many tool calls in one request, in parallel or in series. - [Other](https://mcp-browser-extension.vercel.app/docs/tools/other): Tools not yet categorised. - [Security](https://mcp-browser-extension.vercel.app/docs/security): Deny-all by default. Domain allowlist, mutation and eval gates, redaction, the audit log, and the pairing token. - [Architecture](https://mcp-browser-extension.vercel.app/docs/architecture): The build blueprint: three worlds, one executor interface, the wire protocol, the full tool surface, the extension manifest and the security model. - [Compare](https://mcp-browser-extension.vercel.app/docs/compare): How chrome-mcp differs from Playwright MCP, Puppeteer MCP and Browser Use, and when you would pick each. - **Project** - [Develop](https://mcp-browser-extension.vercel.app/docs/develop): Build from source, run the tests, and load the extension from a git clone. - [Changelog](https://mcp-browser-extension.vercel.app/docs/changelog): Every release of @mehmoodqureshi/chrome-mcp, newest first. - [Privacy policy](https://mcp-browser-extension.vercel.app/docs/privacy): What the MCP Browser Extension does with page content, where data goes, and what it never sends anywhere. ## Blog - [Blog index](https://mcp-browser-extension.vercel.app/blog): every post, newest first. - [MCP browser extension: what it is and when you need one](https://mcp-browser-extension.vercel.app/blog/what-is-an-mcp-browser-extension): What an MCP browser extension is, how it differs from a browser MCP server that launches its own Chromium, how the pieces connect, and when headless is better. - [Claude Code browser access: connect it to your logged-in Chrome](https://mcp-browser-extension.vercel.app/blog/claude-code-browser): Set up Claude Code browser access through an MCP server and a Chrome extension, so it works in the Chrome you are signed into. Exact commands and fixes. - [Cursor browser MCP: give Cursor your real, signed-in Chrome](https://mcp-browser-extension.vercel.app/blog/cursor-browser-mcp): Set up a Cursor browser MCP server that drives your real Chrome: the exact mcp.json, the extension, pairing, use cases like local dev and dashboards, limits. - [VS Code Copilot browser MCP: let Copilot use your real Chrome](https://mcp-browser-extension.vercel.app/blog/vscode-copilot-browser-mcp): Set up a VS Code Copilot browser MCP server that drives your logged-in Chrome: mcp.json, code --add-mcp, trust, pairing, the allowlist and a first task. - [Codex browser MCP: use your logged-in Chrome from OpenAI Codex](https://mcp-browser-extension.vercel.app/blog/codex-browser-mcp): Set up chrome mcp in OpenAI Codex: add the server with codex mcp add or config.toml, pair the extension, allow domains, and run a first task in your Chrome. - [Best browser MCP servers in 2026, picked by the job you need](https://mcp-browser-extension.vercel.app/blog/best-browser-mcp-servers): The best browser MCP depends on the job: testing, debugging, logged-in pages, cloud scale or autonomous agents. Ten servers checked against their own docs. - [Claude in Chrome vs Chrome MCP: which browser tool to use](https://mcp-browser-extension.vercel.app/blog/claude-in-chrome-vs-mcp-browser-extension): Claude in Chrome vs Chrome MCP, verified from the docs: when Anthropic's own extension is the better pick, and when an MCP browser extension fits better. - [Chrome DevTools MCP vs Playwright MCP vs an MCP extension](https://mcp-browser-extension.vercel.app/blog/chrome-devtools-mcp-vs-playwright-mcp): Chrome DevTools MCP vs Playwright MCP, plus Browser MCP, mcp-chrome and Browser Use: what each is built for, verified from their docs, and when to pick each. - [Can AI agents log in to websites? What actually works in 2026](https://mcp-browser-extension.vercel.app/blog/can-ai-agents-log-in-to-websites): Can AI agents log in to websites? Yes, four ways: typed passwords, saved cookies, OAuth APIs, or your own signed-in browser. Trade-offs and when to use each. ## Optional - [Full text of the docs and blog](https://mcp-browser-extension.vercel.app/llms-full.txt)