Chrome DevTools
Control and inspect a live Chrome browser for automation and debugging.
Chrome DevTools
Control and inspect a live Chrome browser for automation and debugging. With Lunar.dev MCPX, the MCP Gateway for secure and governed tool access, you connect the Chrome DevTools MCP server to Claude, ChatGPT, Cursor, and any MCP client through one gateway that routes, authenticates, and governs every Chrome DevTools tool call against your policies.
Why MCPX
MCPX is Lunar.dev's MCP Gateway. It sits between your AI agents and your MCP servers as a single gateway for every tool call, routing, authenticating, and governing traffic against your policies. Connect Chrome DevTools once and govern it everywhere: role-based access per agent with on-behalf-of attribution, real-time visibility, and an immutable audit trail of who did what, all deployable inside your own VPC.
Tools content
- click · Write
Clicks on the provided element. - drag · Write
Drag an element onto another element. - fill · Write
Type text into an input, text area or select an option from a <select> element. - fill_form · Write
Fill out multiple form elements (inputs, selects, checkboxes, radios) at once. - handle_dialog · Write
If a browser dialog was opened, use this command to handle it. - hover · Write
Hover over the provided element. - press_key · Write
Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations). - type_text · Write
Type text using keyboard into a previously focused input. - upload_file · Write
Upload a file through a provided element. - click_at · Write
Clicks at the provided coordinates (requires flag: --experimentalVision=true). - close_page · Write
Closes the page by its index. The last open page cannot be closed. - list_pages · Read-only
Get a list of pages open in the browser. - navigate_page · Write
Go to a URL, or back, forward, or reload. Use project URL if not specified otherwise. - new_page · Write
Open a new tab and load a URL. Use project URL if not specified otherwise. - select_page · Write
Select a page as a context for future tool calls. - wait_for · Read-only
Wait for the specified text to appear on the selected page. - emulate · Write
Emulates various features on the selected page. - resize_page · Write
Resizes the selected page's window so that the page has specified dimension. - performance_analyze_insight · Read-only
Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording. - performance_start_trace · Read-only
Start a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed.
Frequently asked questions
What is the Chrome DevTools MCP server?
Control and inspect a live Chrome browser for automation and debugging. Through Lunar.dev MCPX, Chrome DevTools connects to any MCP-compatible AI client behind a single governed gateway.
How do I connect Chrome DevTools to MCPX?
Add the Chrome DevTools server in the MCPX control plane or your app.yaml, then point your AI client at your MCPX gateway. MCPX handles no authentication and routes every Chrome DevTools call through the gateway.
Is the Chrome DevTools MCP server official?
Yes. Chrome DevTools is an official, vendor-published MCP server, and MCPX governs it like any other server in your catalog.
What authentication does Chrome DevTools use with MCPX?
Chrome DevTools requires no authentication. MCPX still controls which agents and users are allowed to call it through role-based access control.
How many tools does Chrome DevTools expose in MCPX?
Chrome DevTools exposes 45 tools. In MCPX you can enable or disable each tool per agent for least-privilege access.
