Claude Code Browser MCP Setup — Documentation skill for Claude Code
Setup documentation for using Chrome DevTools MCP server with Claude Code.
How to install Claude Code Browser MCP Setup
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open haasonsaas/claude-code-browser-mcp-setup and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Claude Code Browser MCP Setup does
Setup documentation for using Chrome DevTools MCP server with Claude Code.
Alternatives in Documentation
- Doc Co-authoring — Guide users through structured workflow for co-authoring documentation 94.1k ★
- Context7 — claude-plugins-official Up-to-date library documentation lookup 50.1k ★
- Notion Research Documentation — Research Notion content and synthesize findings into structured briefs 14.6k ★
README
Claude Code Browser MCP Setup
Documentation for using the Chrome DevTools MCP server with Claude Code to enable browser automation and web interaction capabilities.
Overview
This setup allows Claude Code to interact with Chrome browser through the Model Context Protocol (MCP). The Chrome DevTools MCP server provides tools for:
- Page navigation and management
- Taking snapshots and screenshots of web pages
- Clicking, filling forms, and interacting with page elements
- Network request monitoring
- Performance analysis
- JavaScript execution in browser context
Installation
1. Install the Chrome DevTools MCP Server
npm install -g @modelcontextprotocol/server-chrome-devtools
Or using npx (no installation required):
npx @modelcontextprotocol/server-chrome-devtools
2. Configure Claude Code
Add the MCP server to your Claude Code configuration file at `~/.config/claude/claude_desktop_config.json`:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-chrome-devtools"
]
}
}
}
If you installed globally, you can use:
{
"mcpServers": {
"chrome-devtools": {
"command": "mcp-server-chrome-devtools"
}
}
}
3. Launch Chrome with Remote Debugging
The MCP server connects to Chrome via the Chrome DevTools Protocol. You need to launch Chrome with remote debugging enabled:
**macOS:**
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
**Linux:**
google-chrome --remote-debugging-port=9222
**Windows:**
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
4. Restart Claude Code
After configuration, restart Claude Code to load the MCP server.
Available Tools
The Chrome DevTools MCP provides the following tools (all prefixed with `mcp__chrome-devtools__`):
Page Management
- `l
Related Skills
MarkSight
Browser-only Markdown editor that packages any document into a Claude Agent Skill (SKILL.md / .skill bundle) i
My Harness Library
Self-hosted, searchable inventory of every Claude Code skill, agent, command, plugin and MCP server — with an
Adding New Preset
Use when adding a new preset screening strategy to the MCP server. Ensures presets follow established patterns
LLMs Txt MCP
Lean MCP server for fast llms.txt documentation access
Fetch MCP
Comprehensive HTTP fetch MCP server with SSRF protection, HTML-to-markdown, and robots.txt awareness
Claude Code Memory Stack
A complete, runnable template for giving Claude Code a persistent memory: a Markdown knowledge vault, skills,
Related Agents
Browser Executor
Browser automation agent that executes test scenarios using Chrome DevTools MCP integration with enhanced auto
Browser Analysis Agent
You are a specialized read-only agent for browser content analysis and web inspection. Your capabilities: - Na
Stack Advisor
Выбор стека под bottleneck архитектуры. Учитывает 2026 tech-updates (opendataloader-pdf, VoxCPM2, chrome-devto