Chromedevtoolsmcp
- Updated May 25, 2026
- clauxel/chrome-devtools-session-mcp-mcp
Chrome DevTools Session MCP is a MCP server that connects AI coding agents to remote Chrome DevTools sessions with verdicts, receipts, and usage logs.
About
Chrome DevTools Session MCP is a paid remote Model Context Protocol server from Clauxel that exposes AI agent browser DevTools workflows over streamable HTTP. developers and small teams who ship web apps with Claude Code, Cursor, or similar hosts use it when local browser debugging is awkward to script from the agent or when they want consistent, logged outcomes instead of ad-hoc console paste. The registry entry describes a product focused on verdicts, receipts, and usage logs so automation runs stay explainable after the fact. You register the remote URL in your MCP client, authenticate with a Bearer token from the Clauxel product site, and let the agent invoke DevTools-oriented tools rather than maintaining a custom Chrome bridge. It complements agent skills for testing and front-end work: this is transport and tooling, not a methodology skill. Expect a commercial subscription; pair it with your own test plans and security review of what the agent is allowed to drive in the browser.
- 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)
Chromedevtoolsmcp by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --transport http chromedevtoolsmcp-mcp https://chromedevtoolsmcp.clauxel.com/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Last updated | May 25, 2026 |
| Repository | clauxel/chrome-devtools-session-mcp-mcp ↗ |
What it does
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.
Who is it for?
Best when you're automating repro steps, DOM checks, or DevTools workflows from Claude Code or Cursor without self-hosting a Chrome MCP bridge.
Skip if: Skip if you need a free, fully local browser stack only, or workflows with no paid third-party MCP budget.
What you get
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
By the numbers
- Registry version 1.0.0
- Single remote endpoint type: streamable-http
- Authentication: Bearer token header
README.md
Chrome DevTools Session MCP
Hosted MCP for AI agent browser DevTools MCP.
Chrome DevTools Session MCP is a paid remote MCP endpoint for AI agent browser DevTools MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-ready workflow evidence for AI agents and coding teams.
Public Endpoints
- Website: https://chromedevtoolsmcp.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- MCP endpoint: https://chromedevtoolsmcp.clauxel.com/mcp
- Server card: https://chromedevtoolsmcp.clauxel.com/.well-known/mcp/server-card.json
- Registry name:
com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp
Access
This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.
Authorization: Bearer <token>
Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.
Tools
inspect_page_stateread_console_errorssummarize_network_waterfallexport_devtools_receipt
Quick Start
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.
Useful Links
- Product page: https://chromedevtoolsmcp.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- Pricing: https://chromedevtoolsmcp.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25#pricing
- Server card: https://chromedevtoolsmcp.clauxel.com/.well-known/mcp/server-card.json
- MCP endpoint: https://chromedevtoolsmcp.clauxel.com/mcp
Status
This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.
Recommended MCP Servers
1stDibs MCPMCP server for browsing and searching items on 1stDibs marketplace.
2Captcha MCPFull 2Captcha API (43 tools) for Claude Code: 31 captcha solvers + management + webhook.1
4fetch MCPFetch a URL and get clean Markdown with metadata.
Acrawl MCPAutonomous web crawler.11
Agentfetch MCPToken-budgeted web fetch for AI agents — auto-routes Jina, FireCrawl, Trafilatura, PDF.3AgenticTotem Web Extractor MCPAI web extraction: send URLs + a JSON Schema, get clean structured data.How it compares
Paid remote browser DevTools MCP integration, not a local Playwright skill or a generic web-scraping script.
FAQ
Who is Chrome DevTools Session MCP for?
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.