Chrome MCP Server logo

Chrome MCP Server

by adejaimejr

A Node.js server that integrates with the Chrome DevTools extension to provide debugging and monitoring functionalities for Cursor AI. It acts as a bridge between the Chrome DevTools extension and the Cursor AI.

View on GitHub

Last updated: N/A

What is Chrome MCP Server?

The Chrome MCP Server is a Node.js server that acts as a bridge between the Chrome DevTools extension and the Cursor AI, enabling debugging and monitoring functionalities.

How to use Chrome MCP Server?

The server can be run directly from GitHub, installed globally via npm, or published to npm. Configuration involves adding a new MCP server in Cursor settings with the appropriate command. Detailed installation steps are provided for local setup, including cloning the repository, installing dependencies, and building the executable.

Key features of Chrome MCP Server

  • Captures console logs and errors

  • Monitors network requests (successes and errors)

  • Captures screenshots

  • Inspects selected elements

  • Clears logs

  • Automatic port handling

  • JSON output enforcement

Use cases of Chrome MCP Server

  • Debugging Cursor AI applications

  • Monitoring network activity

  • Capturing screenshots for analysis

  • Inspecting DOM elements

  • Troubleshooting errors

  • Integrating Chrome DevTools with Cursor AI

FAQ from Chrome MCP Server

What is the purpose of the Chrome MCP Server?

It provides debugging and monitoring functionalities for Cursor AI by integrating with the Chrome DevTools extension.

How do I install the Chrome MCP Server?

You can run it directly from GitHub, install it globally via npm, or publish it to npm. Detailed instructions are provided in the README.

How do I configure the server in Cursor?

Go to Cursor settings, navigate to 'Extensions' > 'MCP', and add a new MCP server with the appropriate command.

What if I encounter the error 'Falha ao analisar a resposta JSON' or 'Unexpected token... is not valid JSON'?

Ensure you are using version 1.2.0 or higher, update the repository with git pull, and rebuild with npm run build. Also, verify the path to mcp-server.js.

What if I encounter the error 'EADDRINUSE: address already in use'?

The server automatically tries alternative ports. If the problem persists, try manually terminating the process using port 3000 or define a specific port using the PORT environment variable.