ConsoleSpy MCP Server

Overview

The ConsoleSpy MCP Server captures browser console logs and makes them available to AI models through the Model Context Protocol (MCP). This allows for real-time debugging, error monitoring, and in-depth application analysis directly within AI-assisted development environments.

Key Features

Available Tools

Quick Reference

Detailed Usage

use_mcp_tool({
  server_name: "consolespy",
  tool_name: "get_logs",
  arguments: {}
});

use_mcp_tool({
  server_name: "consolespy",
  tool_name: "clear_logs",
  arguments: {}
});

Installation

{
  "mcpServers": {
    "consolespy": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway",
        "--port",
        "8766",
        "--stdio",
        "node",
        "console-spy-mcp.js"
      ],
      "env": {
        "CONSOLE_SERVER_URL": "http://localhost:3333/mcp"
      }
    }
  }
}

When to Use This Server

ConsoleSpy is useful in the same situations you'd otherwise spend minutes copy-pasting browser console output into a chat window. Because it captures logs continuously, an AI assistant can act on them without you switching tabs:

• Debugging loops — Reproduce a bug in the browser, then ask the assistant to read the captured logs and propose a fix. No manual copy-paste between browser and editor.
• Runtime error triage — When an error appears intermittently, the server keeps the recent console history available so the assistant can correlate the failing action with the logged output.
• Regression checks — Run a feature, clear logs with clear_logs, exercise the flow again, and have the assistant review what changed.

For production error monitoring, pair it with Sentry MCP; for full browser automation and assertions, see Playwright MCP.

Frequently Asked Questions

Sources