ConsoleSpy
local-only server
The server can only run on the client’s local machine because it depends on local resources.
Integrations
Provides a browser extension for Chrome that captures console logs and sends them to the ConsoleSpy server
Hosts the repository for ConsoleSpy that users can clone to set up the MCP server
ConsoleSpy: An MCP Server for Cursor
A tool that captures browser console logs and makes them available in Cursor IDE through the Model Context Protocol (MCP).
Overview
This tool consists of:
- A server that captures console logs from your browser
- An MCP server that makes these logs available to Cursor
- A browser extension that sends console logs to the server
Installation
Server Setup
- Clone this repository:Copy
- Install dependencies:Copy
- Run the setup script to configure the MCP connection for Cursor:Copy
Browser Extension Installation
- Install the extension from the Chrome Web StoreORLoad the extension in developer mode:
- Open Chrome and go to
chrome://extensions/
- Enable "Developer mode" (toggle in the top-right corner)
- Click "Load unpacked" and select the
extension
folder from this repository
- Open Chrome and go to
Usage
Starting the Servers
- Start the console log server:Copy
- In a separate terminal, start the MCP server:Copy
Alternatively, you can use the start script to launch both servers at once:
Configuring Cursor
After running the setup script, you still need to manually add the MCP server in Cursor:
- Go to Settings > Features > MCP in Cursor
- Add a new MCP server with:
- Name: ConsoleSpy
- Type: sse
- URL: http://localhost:8766/sse
Using the Extension
- Click the extension icon in your browser to toggle it on/off
- When enabled, all console logs from the current tab will be sent to the server
- In Cursor, you can now access these logs through the MCP interface
Customizing
Changing the Console Log Server Port
If you need to use a different port for the console log server (default is 3333), you'll need to update the port in multiple places:
- In
mcp-server.js
, change the port variable:Copy - In
console-spy-mcp.js
, update the URL to match your new port:Copy - In the browser extension's
content.js
, update the server URL:Copy - If using
start-servers.sh
, update the port reference there as well.
Important: You must use the same port number in all locations. We recommend doing a global search for "3333" in the project files and replacing all instances with your desired port number to ensure consistency.
If you're testing locally with another application already using port 3333, changing this port is essential for the tool to work correctly.
Troubleshooting
- Make sure both servers are running
- Verify the browser extension is enabled for the tab you're debugging
- Check that you've added the MCP server in Cursor's settings
- If logs aren't appearing, try refreshing the page or restarting the servers
License
This server cannot be installed
A tool that captures browser console logs and makes them available in Cursor IDE through the Model Context Protocol (MCP).