Connect AI Agents via Chrome DevTools MCP

This page follows the standard Google/Chrome MCP path:

Use this when you want Claude, Gemini, Codex, or other MCP clients to control and inspect a live Chrome session while working with MikroTik docs.

Standard MCP config

The baseline server config is:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Quick setup by client

Claude Code

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Gemini CLI

Project-scoped:

gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest

Global:

gemini mcp add -s user chrome-devtools npx chrome-devtools-mcp@latest

Codex CLI

codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Google options you can enable or disable

Chrome DevTools MCP includes Google-integrated behavior you can tune with flags:

--no-usage-statistics disables usage telemetry for the MCP server.
--no-performance-crux disables CrUX lookups during performance analysis.
--channel=stable|beta|dev|canary chooses which Chrome channel to run.
--autoConnect attaches to a running Chrome 144+ profile after remote debugging is enabled.

Example with Google options disabled:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--headless",
        "--no-usage-statistics",
        "--no-performance-crux"
      ]
    }
  }
}

Connect to an already-running Chrome

If your agent runs in a sandbox, point MCP to a running browser:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222"
      ]
    }
  }
}

Start Chrome with remote debugging and a non-default profile:

/usr/bin/google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-stable

Verify it works

Use this prompt in your MCP client:

Check the performance of https://mikrotikdocs.fyi

You should see the agent open Chrome and return navigation/performance output from DevTools MCP tools.

Notes

This replaces the old token-based @jason.today/webmcp workflow.
Keep chrome-devtools-mcp@latest to stay aligned with current Chrome and client integrations.
For full tool and flag reference, use the upstream README: https://github.com/ChromeDevTools/chrome-devtools-mcp