About Consolespy
Consolespy is an MCP server published by mgsrevolver in the Developer Tools category: this tool captures browser console logs and makes them available to Cursor IDE through the Model Context Protocol (MCP). It has been installed 0 times through Conduid.
The repository has 12 stars and 6 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx consolespyThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Consolespy
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
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:
git clone https://github.com/mgsrevolver/consolespy.git cd consolespy -
Install dependencies:
npm install -
Run the setup script to configure the MCP connection for Cursor:
./setup.sh
Browser Extension Installation
-
Install the extension from the Chrome Web Store
OR
Load 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
extensionfolder from this repository
- Open Chrome and go to
Usage
Starting the Servers
-
Start the console log server:
node mcp-server.js -
In a separate terminal, start the MCP server:
npx supergateway --port 8766 --stdio "node console-spy-mcp.js"
Alternatively, you can use the start script to launch both servers at once:
./start-servers.sh
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:const port = 3333; // Change to your desired port -
In
console-spy-mcp.js, update the URL to match your new port:const CONSOLE_SERVER_URL = 'http://localhost:3333/mcp'; // Change 3333 to your port -
In the browser extension's
content.js, update the server URL:const serverUrl = 'http://localhost:3333/console-logs'; // Change 3333 to your port -
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
README mirrored from the source repository 4 months ago. The original is authoritative.