ConsoleSpy MCP

MCP开发工具

提供方 mgsrevolver

开发工具 未标注 无需鉴权 社区 / 第三方

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

一句话选型结论

按资料字段整理

ConsoleSpy MCP 属于开发工具类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
ConsoleSpy MCP当前 未标注 未标注 本地部署 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方mgsrevolver上游标注的维护方 mgsrevolver
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

3.2 KB
来自项目仓库与上游目录的原文,未做删改

ConsoleSpy

> Archived August 2026. ConsoleSpy piped browser console logs into an AI coding agent back when there was no supported way to do that. There are now several, shipped by the browser and model vendors themselves. Use one of those instead — see below. The code stays up for reference; it is no longer maintained.

Use these instead

Tool Notes
Chrome DevTools MCP Google's official server. Console messages with source-mapped stack traces, plus network, performance, and DOM inspection.
Chrome DevTools auto-connect Chrome 144+. Attaches the MCP server to the Chrome you already have open, with a per-session permission prompt. No debug port, no separate profile.
Claude in Chrome Anthropic's extension plus native messaging bridge. Run claude --chrome and the agent reads console output from your real, logged-in browser. Requires a paid Anthropic plan.
Safari MCP server Apple's equivalent for WebKit, shipped July 2026.

What this was

In March 2025, MCP was about four months old and agents were effectively blind to the browser: you debugged by copy-pasting console output into a chat window. ConsoleSpy closed that loop with three pieces — a Chrome extension that hooked console.* in the active tab, a local Express collector on port 3333, and an MCP server exposing those logs to Cursor over SSE.

Why it's archived

The specific thing ConsoleSpy did that alternatives couldn't was capture logs passively, from the real browser profile you were already signed into. That mattered more over time, not less: Chrome 136 blocked remote debugging on default profiles, so every tool built on the Chrome DevTools Protocol had to launch a throwaway profile with none of your sessions in it. An extension didn't have that problem.

That gap is now closed from both directions. Chrome 144's auto-connect grants a debugging session against your live browser behind a permission dialog, and Claude in Chrome does it through a native messaging bridge with no port and no MCP configuration at all. Both are first-party, both cover far more than console logs, and neither asks you to run two processes.

What I'd do differently

  • Configuration by find-and-replace. Port 3333 was hardcoded in four files, and the README's advice was to grep for it. One config value, read once, would have cost nothing.
  • Two processes and an SSE bridge. The collector and the MCP server ran separately, glued together with supergateway. Plain stdio would have removed both the second process and the manual client setup.
  • Coupled to one editor instead of the protocol. The package was named console-to-cursor-mcp. MCP's whole point is that the client is interchangeable; the naming and docs should have reflected that.

One problem from 2025 does remain unsolved, and it's the interesting one: console and network output floods an agent's context window. Anthropic's own docs now advise telling the agent which patterns to look for, "since logs can be verbose." Capture was the easy half. Triage — deduplicating by stack signature, diffing against a clean baseline, surfacing only what changed since the last edit — is still mostly manual.

License

MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
ConsoleSpy MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

ConsoleSpy MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

ConsoleSpy MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

ConsoleSpy MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

ConsoleSpy MCP 能提供哪些能力?

资料显示能力标签包括 调试工具、日志记录、开发工具。具体工具清单以官方文档为准。

ConsoleSpy MCP 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

ConsoleSpy MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。