Ory logo

Google Chrome DevTools MCP Server

Google's Chrome DevTools MCP server allows AI agents to inspect, debug, and automate web applications directly within Google Chrome. It provides comprehensive programmatic access for agents to inspect the live Document Object Model (DOM), monitor and analyze network traffic, evaluate JavaScript expressions, capture performance timelines, and examine browser console logs.

Google logo

Google Chrome DevTools MCP Server

Benefits with Ory + Google Chrome DevTools MCP Server

Google's Chrome DevTools MCP server hands your agents a live Chrome browser for debugging, from page structure and console output to network requests and performance traces. The same browser can also be clicked, typed into, and scripted, sometimes in sessions signed in to real accounts. Ory Agent Security checks each tool call against the user and agent behind it, so a debugging agent can inspect a page while only the test agents you approve can drive it.

Use Cases

Agent IAM

Page inspectors work at Read, test agents click through flows at Write, script runners get Admin, and you set Block on agents that never need a browser.

Explore Agent IAM

Core Functionality

  1. Read, write, admin, or no access

    Ory Agent Security classifies every tool on the Chrome DevTools MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for debugging agents that inspect pages, write for test agents that click and type through flows, admin for agents you'd trust with your own browser session, and no access for agents with no reason to drive a browser.

  2. Enforced before execution

    Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied script run stops before it reaches Chrome, with nothing to roll back and no gateway to deploy.

  3. Observe, then enforce

    Observe mode shows which agents drive the browser or run scripts and for which users without blocking anything, so you can apply Ory's pre-built policy for the Chrome DevTools MCP server and enforce it on your own schedule.

  4. Complete audit trail

    Every allow and deny decision on the Chrome DevTools MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent acted in a browser session and on whose behalf.