chrome

This MCP server acts as a bridge between the Chrome DevTools extension and Cursor AI, enabling debugging and monitoring for web pages analyzed by Cursor. It provides tools to capture console logs and errors, monitor network requests (both successes and failures), take screenshots, inspect the selected DOM element, and clear stored logs. The server exposes these capabilities via MCP endpoints that Cursor can query or invoke, allowing you to programmatically retrieve logs, network activity, or element data during a debugging session. Typical usage involves launching the server locally, configuring Cursor to point at the local MCP instance, and then using the available tools like getConsoleLogs, getConsoleErrors, getNetworkErrorLogs, getNetworkSuccessLogs, takeScreenshot, getSelectedElement, and wipeLogs to gather and inspect telemetry from the page under test.

Prerequisites:

• Node.js 14+ and npm installed
• Basic familiarity with MCP and Cursor configuration

Option A: Run directly from GitHub (no local install)

• Ensure you have npm and npx installed
• Start the server with: npx github:adejaimejr/chrome-mcp-server

Option B: Install globally and run

• Install globally: npm install -g github:adejaimejr/chrome-mcp-server
• Run the server: chrome-mcp-server

Option C: Publish to npm and run via npx

• If you publish without a scope: npm login npm publish Then you can run: npx chrome-mcp-server
• If you publish with a scope (recommended for organization): Modify package.json name to "@adejaimejr/chrome-mcp-server" and publish publicly: npm publish --access public Then run: npx @adejaimejr/chrome-mcp-server

Option D: Local clone and build (for development)

• Clone the repository: git clone https://github.com/adejaimejr/chrome-mcp-server.git
• Enter the directory: cd chrome-mcp-server
• Install dependencies: npm install
• Build the executable (if applicable): npm run build
• Use the absolute path to the built file in Cursor (Windows example): node C:\path\to\chrome-mcp-server\dist\mcp-server.js
• For Linux/Mac, use: node /path/to/chrome-mcp-server/dist/mcp-server.js

Tips and notes:

• The server aims to emit output strictly as JSON. If you encounter non-JSON output, ensure you’re using v1.2.0 or later and rebuild if needed.
• Automatic port handling: the server will try 3000, then 3001, 3002, etc., if the default port is in use. You can override the port by setting the PORT environment variable, e.g. PORT=3001.
• Security: this server is intended for local development. Do not expose it publicly without additional security controls.
• Common MCP tools supported: getConsoleLogs, getConsoleErrors, getNetworkErrorLogs, getNetworkSuccessLogs, takeScreenshot, getSelectedElement, wipeLogs.
• If you automate Cursor configuration, you can omit the --mcp flag on recent versions, as the server auto-detects Cursor invocation.