Chromedevtoolsmcp MCP

What chromedevtoolsmcp-mcp does

The chromedevtoolsmcp-mcp MCP server gives AI agents access to a hosted browser DevTools service over MCP. Its interface is organized around four structured JSON tools: inspect_page_state, read_console_errors, summarize_network_waterfall, and export_devtools_receipt.

These tools cover distinct parts of a browser debugging or evidence workflow. Page inspection can be used to examine the current page state, while console and network tools focus on runtime errors and request activity. The receipt tool is intended for exporting a record of the DevTools work. The supplied material does not define each tool's input schema or response fields, so those details should be checked through the service's MCP metadata or client tooling.

How it works

The service is hosted remotely at https://chromedevtoolsmcp.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint using Streamable HTTP. Production requests must include a bearer token in the HTTP authorization header:

Authorization: Bearer <token>

The product website is the source for choosing a plan and obtaining or requesting a token. The service also publishes a server card at https://chromedevtoolsmcp.clauxel.com/.well-known/mcp/server-card.json, which can help clients or operators discover its public metadata.

Setup and configuration

To configure the chromedevtoolsmcp-mcp MCP server, open the product website, select a plan, and create or request an API token. Add the MCP endpoint to a client that supports remote Streamable HTTP servers, then configure the client to send the token as a bearer credential.

The endpoint is not intended to be used as an unauthenticated browser page. The documentation states that unauthenticated visits return a JSON error rather than internal service details. No environment variable names or local configuration files are specified in the supplied material; authentication is described through the HTTP header instead.

Tools and capabilities

The available MCP tools are:

• inspect_page_state — inspect browser page state.
• read_console_errors — read console errors.
• summarize_network_waterfall — summarize network waterfall activity.
• export_devtools_receipt — export a DevTools receipt.

Together, these tools support agent workflows that need browser diagnostics and a record of the resulting DevTools activity. The documentation also identifies usage receipts and audit-ready workflow evidence as service concerns, but it does not specify retention, receipt formats, quotas, or reporting APIs.

Limitations and notes

The chromedevtoolsmcp-mcp MCP server is a paid hosted service, so production use depends on an account plan and an issued token. It is not presented as a package that runs locally. The repository is a public documentation and directory-submission reference; it does not contain the private production implementation.

The provided material does not state which browser versions, operating systems, authentication providers, or individual MCP clients are supported. Client compatibility should therefore be confirmed against the client's Streamable HTTP support and the service's current documentation. Tool parameters, response schemas, pricing details, and operational limits are also not included here.