1. Conduid
  2. Developer Tools
  3. Consolespy
MCP server · Developer Tools

Consolespy

This tool captures browser console logs and makes them available to Cursor IDE through the Model Context Protocol (MCP).

Unclaimed MIT last commit a year ago devtools
54Fair

Scored 4 months ago · breakdown

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

Install
npx consolespy

This 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

I know everything about Consolespy. Ask me about installation, configuration, usage, or troubleshooting.

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:

  1. A server that captures console logs from your browser
  2. An MCP server that makes these logs available to Cursor
  3. A browser extension that sends console logs to the server

Installation

Server Setup

  1. Clone this repository:

    git clone https://github.com/mgsrevolver/consolespy.git
    cd consolespy
    
  2. Install dependencies:

    npm install
    
  3. Run the setup script to configure the MCP connection for Cursor:

    ./setup.sh
    

Browser Extension Installation

  1. 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 extension folder from this repository

Usage

Starting the Servers

  1. Start the console log server:

    node mcp-server.js
    
  2. 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:

  1. Go to Settings > Features > MCP in Cursor
  2. Add a new MCP server with:
    • Name: ConsoleSpy
    • Type: sse
    • URL: http://localhost:8766/sse

Using the Extension

  1. Click the extension icon in your browser to toggle it on/off
  2. When enabled, all console logs from the current tab will be sent to the server
  3. 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:

  1. In mcp-server.js, change the port variable:

    const port = 3333; // Change to your desired port
    
  2. 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
    
  3. In the browser extension's content.js, update the server URL:

    const serverUrl = 'http://localhost:3333/console-logs'; // Change 3333 to your port
    
  4. 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

MIT License

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Consolespy

How do I install Consolespy?

Run npx consolespy, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Consolespy safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Consolespy still maintained?

The last commit was a year ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.