Skip to content
Agentmart
Submit a tool

How to connect Chrome to Cursor

This guide connects Chrome DevTools MCP to Cursor. ChromeDevTools publishes it, the listing does not flag it as the vendor's own, it runs on your machine through npx, and no API key is listed. Expect to edit one JSON config and then read the MCP logs. Install data comes from the listing and Cursor's documentation.

Updated Oct 26, 2026 · Built from catalog data; how we rank and grade

Checked against Cursor's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

Before you start

  • Cursor installed and able to start.
  • Node.js with npx (the server starts with npx).
  • No API key is listed for Chrome DevTools MCP.

  1. 1. Check what you need

    Cursor needs Node.js to launch this server with npx. Check for it with node --version first.

    Check that it is installed
    node --version
    • The listing names no required key.

  2. 2. Add Chrome DevTools MCP to Cursor

    The entry below goes in a Cursor mcp.json file, either per project or in your home directory, and describes how to start Chrome DevTools MCP with npx.

    Add this to .cursor/mcp.json in the project, or to ~/.cursor/mcp.json for every project.cursor/mcp.json
    {
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@1.12.0"
      ]
    }
  }
}

  3. 3. Restart or reload if it does not appear

    If Chrome DevTools MCP is absent from Cursor, the notes here cover the docs' guidance on restarting and the approval prompt for tools.

    • The docs do not say whether editing mcp.json needs a restart. They tell you to restart Cursor after updating files of a custom local server.
    • Cursor asks for approval before an agent uses an MCP tool unless you allowlist it.

Check that it works

Open the logs to confirm the connection, then see whether the tool list matches the catalog's count of 68.

  • Open the Output panel (Cmd+Shift+U on macOS), choose MCP Logs, and look for connection errors. A working server lists its tools under Available Tools; agent mcp list shows connection state from the terminal.
  • Once it is connected, Cursor should list its tools; the catalog records 68 for Chrome DevTools MCP, including analyze_heapsnapshot_contexts, click and click_at.

Troubleshooting

A server fails or an npm-based server misbehaves after an update
Check the MCP Logs channel in the Output panel. For npm-based servers the docs suggest removing the server, running npm cache clean --force, and adding it again. Source

Reported by other users

Issues in the server's repository (ChromeDevTools/chrome-devtools-mcp) about installing or starting it, as of Oct 26, 2026. They are links, not fixes: open one to see whether it was resolved.

Security notes

  • Publisher: ChromeDevTools, not listed as the vendor's own server; license Apache-2.0.
  • It runs on your machine with your user account's permissions, so it can reach any file or network resource you can. Read its source before you give it access: https://github.com/ChromeDevTools/chrome-devtools-mcp.
  • The listing declares no required keys; use a token with the narrowest scope if the service asks for one.
  • This listing has no security grade: Agent Market has not published security grades yet, so the choice is yours to make from the source and the permissions.

How we grade security · Trust policy

Servers and skills in this guide

Related reading: other Chrome servers, a comparison, and the general Cursor guide.

  1. 1
    Chrome DevTools MCP

    ChromeDevTools

    MCP server for Chrome DevTools

    ★ 54.1KLast active Oct 23, 2026Local (stdio)Claude Code, Codex, VS Code, Cursor +2

Related

Sources

Cite this page

How to connect Chrome to Cursor. Agent Mart. https://agentmart.dev/guides/connect-chrome-to-cursor (last updated 2026-10-26)