HabaAndrei

Custom Chrome Dev MCP — Development skill for Claude Code

Development community

Local-only MCP server that drives the real Chrome you already have open (your profile, your logins, your session) through a companion extension.

How to install Custom Chrome Dev MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open HabaAndrei/custom-chrome-dev-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Custom Chrome Dev MCP does

Local-only MCP server that drives the real Chrome you already have open (your profile, your logins, your session) through a companion extension. 45 tools across navigation, perception, capture, and CDP-backed trusted input that pages receive with isTrusted=true.

Alternatives in Development

Serena — Code Intelligence Advanced code navigation and semantic search 14k ★
Claude Supermemory — Persistent memory across sessions and projects using Supermemory 2.3k ★
Mem0 Chrome Extension — OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc 671 ★

README

Custom Chrome Dev MCP

A **local-only** MCP (Model Context Protocol) server that lets an MCP client - Claude Code, or anything else that speaks MCP - drive **your real Chrome browser** the way a person would. No telemetry, no third-party services, no cloud: everything runs on your machine behind a shared token.

It exposes **53 tools** across navigation, tabs, perception, interaction, trusted input, observability, capture, and storage.

Where this came from

This project is **inspired by Chrome's official browser MCP** - the [**Chrome DevTools MCP**](https://github.com/ChromeDevTools/chrome-devtools-mcp) server published by the Chrome DevTools team, which first made the case that an AI agent should drive a browser through the DevTools Protocol rather than through scraped HTML.

**We are replicating and imitating that idea, not shipping it.** What we borrowed:

The premise - expose the browser to an agent as a set of MCP tools.
Accessibility-first perception - hand the model a compact a11y outline with stable element refs instead of a wall of raw HTML.
The Chrome DevTools Protocol as the input layer - real, trusted events instead of synthetic ones a page can spot and ignore.

Where this project **deliberately diverges**:

	Chrome DevTools MCP	Custom Chrome Dev MCP
Browser	By default launches its own Chrome with a dedicated user-data-dir; can also attach to a running instance via `--browser-url`	Only ever drives the Chrome you already have open
Attachment	Connects to the browser over the DevTools Protocol endpoint	A Chrome extension living inside the browser, pointed at whatever tab you choose
Primary goal	Debugging, inspecting, and profiling a page	Behaving like a human using that page

That last row is the whole point of this repo. Chrome DevTools MCP is a debugging tool that happens to drive a browser; this is an imitation-of-a-person tool that happens to be useful fo