Chromedevtoolsmcp Mcp
Give Claude Code or Cursor a paid remote MCP that drives Chrome DevTools sessions with logged verdicts and receipts while you debug or automate the browser from an agent.
Overview
Chrome DevTools Session MCP is a MCP server for the Build phase that connects AI coding agents to remote Chrome DevTools sessions with verdicts, receipts, and usage logs.
What is this MCP server?
- Remote streamable-http MCP at chromedevtoolsmcp.clauxel.com with Bearer Authorization
- Chrome DevTools Session MCP for AI-driven browser inspection and automation
- Returns structured verdicts, usage logs, and receipts for agent audit trails
- Paid Clauxel remote MCP pattern aligned with server-card.json discovery
- Open-source reference implementation on GitHub (chrome-devtools-session-mcp-mcp)
- Registry version 1.0.0
- Single remote endpoint type: streamable-http
- Authentication: Bearer token header
What problem does it solve?
Agents struggle to debug real browser behavior when DevTools is outside the MCP tool surface and local automation setup eats solo-builder time.
Who is it for?
Indie builders automating repro steps, DOM checks, or DevTools workflows from Claude Code or Cursor without self-hosting a Chrome MCP bridge.
Skip if: Teams that need a free, fully local browser stack only, or workflows with no paid third-party MCP budget.
What do I get? / Deliverables
After you add the remote MCP with a Bearer token, your agent can run DevTools-backed browser actions and get auditable verdicts and receipts back in the conversation.
- Registered remote Chrome DevTools MCP connection in your agent
- Agent-callable browser DevTools operations with verdict and receipt-style responses
- Usage logs suitable for reviewing what the agent ran
Recommended MCP Servers
Journey fit
Browser DevTools access sits in Build because solo builders wire agent tooling and front-end integrations before ship-ready QA. Integrations is the right shelf for hooking an external streamable-http MCP into the agent instead of running Playwright scripts locally.
How it compares
Paid remote browser DevTools MCP integration, not a local Playwright skill or a generic web-scraping script.
Common Questions / FAQ
Who is Chrome DevTools Session MCP for?
Solo and indie developers using AI coding agents who need Chrome DevTools access through MCP with logged verdicts and usage trails.
When should I use Chrome DevTools Session MCP?
Use it during Build when you are integrating agent tooling to inspect, debug, or automate browser behavior and want remote MCP instead of custom local Chrome wiring.
How do I add Chrome DevTools Session MCP to my agent?
Register the streamable-http remote URL https://chromedevtoolsmcp.clauxel.com/mcp in your MCP client and set Authorization to a Bearer token from the Clauxel product website.