ConsoleSpy

ConsoleSpy provides an MCP Server that exposes browser console logs to Cursor through the Model Context Protocol. It wires a local console log receiver, an MCP gateway, and a browser extension so you can capture debugging output from any web page and access it inside Cursor for analysis and workflow automation.

How to use

You connect to ConsoleSpy from Cursor using the MCP interface and then enable the browser extension to start sending logs. The system consists of an HTTP MCP endpoint that Cursor can query for logs, and a local stdio MCP gateway that runs alongside the log receiver. Start both parts, then configure Cursor to point at the MCP endpoint.

How to install

Prerequisites: Node.js and npm must be available on your machine. You will also use a browser extension to capture logs.

# 1) Clone the project
git clone https://github.com/mgsrevolver/consolespy.git
cd consolespy

# 2) Install dependencies
npm install

# 3) Set up the MCP connection for Cursor
./setup.sh

Using the extension and servers

Start the console log receiver and the MCP gateway in separate terminals. The console log receiver runs as a Node.js server, and the MCP gateway exposes an stdio interface for Cursor.

# Start the console log server
node mcp-server.js

# Start the MCP gateway (stdio) on port 8766
npx supergateway --port 8766 --stdio "node console-spy-mcp.js"

Starting both servers together

You can launch both servers at once with a single script if you have one provided in the project.

./start-servers.sh

Configuring Cursor

After you have the server running, add the ConsoleSpy MCP server in Cursor to enable access to the logs.

Name: ConsoleSpy
Type: sse
URL: http://localhost:8766/sse

Using the Extension

Open the extension in your browser and toggle it on. When enabled, all console logs from the current tab are sent to the server and become accessible in Cursor through the MCP interface.

Customizing

If you need to use a different port for the console log server, keep the port consistent across all parts of the setup. Update the port in the server and gateway configuration so Cursor can connect correctly.

Troubleshooting

If logs aren’t appearing, ensure both servers are running, the browser extension is enabled for the tab you’re debugging, and Cursor has the MCP server added in its settings. Try refreshing the page or restarting the servers.