ConsoleSpy FAQs

Question 1

How does ConsoleSpy integrate with Cursor IDE?

Accepted Answer

ConsoleSpy utilizes the Model Context Protocol (MCP) to transmit real-time browser console logs directly to Cursor IDE, providing a seamless debugging experience.  You'll need to configure an MCP server within Cursor's settings to point to ConsoleSpy.

Question 2

Can I customize the console log server port?

Accepted Answer

Yes, you can customize the port.  You'll need to update the port variable in `mcp-server.js`, `console-spy-mcp.js`, the browser extension's `content.js`, and the `start-servers.sh` script if you use it. Ensure the same port is used consistently across all locations.

Question 3

What is ConsoleSpy?

Accepted Answer

ConsoleSpy is a tool that captures browser console logs and makes them available within the Cursor IDE through the Model Context Protocol (MCP). It consists of a server, a browser extension, and MCP server integration.

Question 4

How do I install ConsoleSpy?

Accepted Answer

First, clone the repository and install dependencies. Then, run the setup script to configure the MCP connection for Cursor. Install the browser extension from the Chrome Web Store or load it in developer mode. Detailed steps are available in the project README.

Question 5

What are the main components of ConsoleSpy?

Accepted Answer

ConsoleSpy has three main parts: a server that captures the console logs, an MCP server that shares logs with Cursor, and a browser extension that sends logs to the ConsoleSpy server.

ConsoleSpy

About

Key Features

Use Cases