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_state
• read_console_errors
• summarize_network_waterfall
• export_devtools_receipt

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.

Quick Start

1. Open the website and choose a plan.
2. Create or request an API token.
3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
4. Send JSON-RPC requests with the bearer token.