chrome-devtools-slim

> Chrome Devtools MCP server optimized for AI assistants — Reduce context window tokens by 69.5% while keeping full functionality. Compatible with Claude, ChatGPT, Gemini, Cursor, and all MCP clients.


What is chrome-devtools-slim?

A token-optimized version of the Chrome Devtools Model Context Protocol (MCP) server.

$3

MCP tool schemas consume significant context window tokens. When AI assistants like Claude or ChatGPT load MCP tools, each tool definition takes up valuable context space.

The original chrome-devtools-mcp loads 26 tools consuming approximately ~18,576 tokens — that's space you could use for actual conversation.

$3

chrome-devtools-slim intelligently groups 26 tools into 8 semantic operations, reducing token usage by 69.5% — with zero functionality loss.

Your AI assistant sees fewer, smarter tools. Every original capability remains available.

Performance

| Metric | Original | Slim | Reduction |
|--------|----------|------|-----------|
| Tools | 26 | 8 | -69% |
| Schema Tokens | 3,756 | 1,104 | 70.6% |
| Claude Code (est.) | ~18,576 | ~5,664 | ~69.5% |

> Benchmark Info
> - Original: chrome-devtools-mcp@0.12.1
> - Schema tokens measured with tiktoken (cl100k_base)
> - Claude Code estimate includes ~570 tokens/tool overhead

Quick Start

$3

``bash


Claude Desktop - auto-configure

npx chrome-devtools-slim --setup claude

Cursor - auto-configure

npx chrome-devtools-slim --setup cursor

Interactive mode (choose your client)

npx chrome-devtools-slim --setup
`

Done! Restart your app to use chrome-devtools.

$3

`bash


Claude Code (creates .mcp.json in project root)

claude mcp add chrome-devtools -s project -- npx -y chrome-devtools-slim@latest

Windows: use cmd /c wrapper

claude mcp add chrome-devtools -s project -- cmd /c npx -y chrome-devtools-slim@latest

VS Code (Copilot, Cline, Roo Code)

code --add-mcp '{"name":"chrome-devtools","command":"npx","args":["-y","chrome-devtools-slim@latest"]}'
`

Manual Setup

Click to expand manual configuration options

$3

Add to your claude_desktop_config.json:

| OS | Path |
|----|------|
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |

`json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-slim@latest"]
}
}
}
`

$3

Add to .cursor/mcp.json (global) or /.cursor/mcp.json (project):

`json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-slim@latest"]
}
}
}
`

How It Works

MCPSlim acts as a transparent bridge between AI models and the original MCP server:

`
┌─────────────────────────────────────────────────────────────────┐
│ Without MCPSlim │
│ │
│ [AI Model] ──── reads 26 tool schemas ────→ [Original MCP] │
│ (~18,576 tokens loaded into context) │
├─────────────────────────────────────────────────────────────────┤
│ With MCPSlim │
│ │
│ [AI Model] ───→ [MCPSlim Bridge] ───→ [Original MCP] │
│ │ │ │ │
│ Sees 8 grouped Translates to Executes actual │
│ tools only original call tool & returns │
│ (~5,664 tokens) │
└─────────────────────────────────────────────────────────────────┘
`

$3

1. AI reads slim schema — Only 8 grouped tools instead of 26
2. AI calls grouped tool — e.g., interaction({ action: "click", ... })
3. MCPSlim translates — Converts to original: browser_click({ ... })
4. Original MCP executes — Real server processes the request
5. Response returned — Result passes back unchanged

Zero functionality loss. 69.5% token savings.

Available Tool Groups

| Group | Actions |
|-------|---------|
| get | 2 |
| list | 3 |
| performance | 3 |
| take | 2 |
| page | 5 |
| interaction | 7 |
| control | 3 |

Plus 1 passthrough tool — tools that don't group well are kept as-is with optimized descriptions.

Compatibility

- ✅ Full functionality — All original chrome-devtools-mcp features preserved
- ✅ All AI assistants — Works with Claude, ChatGPT, Gemini, Copilot, and any MCP client
- ✅ Drop-in replacement — Same capabilities, just use grouped action names
- ✅ Tested — Schema compatibility verified via automated tests

FAQ

$3

No. Every original tool is accessible. Tools are grouped semantically (e.g., click, hover, drag → interaction), but all actions remain available via the action` parameter.

$3

AI models have limited context windows. MCP tool schemas consume tokens that could be used for conversation, code, or documents. Reducing tool schema size means more room for actual work.

$3

MCPSlim is a community project. It wraps official MCP servers transparently — the original server does all the real work.

License

MIT

---

Powered by MCPSlim — MCP Token Optimizer


_{Reduce AI context usage. Keep full functionality.}