Skip to main content
Inspect.dev supports two distinct MCP workflows: searching the documentation and debugging a live mobile browser.

Inspect documentation MCP server

The read-only documentation MCP server searches and retrieves Inspect guides. It uses Streamable HTTP and requires no authentication.
  • Server URL: https://docs.inspect.dev/mcp
  • Inspect MCP server card
  • Tools: documentation search and read-only documentation filesystem queries

Debug mobile browsers from MCP agents

Device actions run locally through the Inspect CLI. Inspect exposes a Chrome DevTools Protocol endpoint for the connected mobile browser, so Chrome DevTools MCP, Puppeteer, and other CDP-compatible clients can use the live device. This keeps USB devices and local development servers on the user’s machine instead of sending them to a remote Inspect service.

iOS/WebKit capability matrix

Chrome DevTools MCP exposes Chromium-shaped tools. Inspect implements the parts that have an honest WebKit translation or simulator host assist and returns explicit errors for Chromium-only behavior. MCP transports sometimes return a failed tool call as ordinary text with isError: false. Treat responses containing an explicit failure such as “Unable to”, “was not found”, or “unsupported” as failures. Inspect’s pinned coverage sweep enforces that rule and checks the exact 29-tool inventory of chrome-devtools-mcp@1.6.0.