Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Command wrapper MCP server for coding agents, compression, workflows, and local automation.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"sage": {
"command": "npx",
"args": [
"-y",
"psycgod-sage"
]
}
}
}在终端中运行这条命令
claude mcp add sage -- npx -y psycgod-sage粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sage": {
"command": "npx",
"args": [
"-y",
"psycgod-sage"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"psycgod-sage"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 PsYcGoD 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.6.2)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv), Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
SAGE is a local-first command wrapper for AI coding agents. It keeps full terminal output on your machine, sends agents a clean compressed summary, and tracks proof metrics without uploading your raw logs.
Use it with Claude Code, Codex, Cursor, Windsurf, OpenCode, Cline, custom agents, CI scripts, and normal terminal workflows.
Package installation is passive for package-registry safety. After installing, run sage install once to activate SAGE for supported local AI agents.
pip install psycgod-sage
python -m pip install --upgrade psycgod-sage sage install sage run -- python -m pytest
npm install -g psycgod-sage
npx -y psycgod-sage install npx -y psycgod-sage run -- npm test
After install, restart any open AI-agent sessions. New sessions should read the SAGE instructions automatically and route terminal commands through SAGE.
Example prompt after restarting your AI agent:
Please help me with my general book in this folder.
Natural shortcuts also work:
sage pytest
sage npm test sage git status
These are treated as:
sage run -- pytest
sage run -- npm test sage run -- git status
| Step | Result |
|---|---|
sage install | Activates the machine locally, repairs global/project agent instructions, and verifies activation |
sage run -- | Runs the command, stores raw output locally, and returns a compact useful summary |
| Agent memory/hooks | Tell supported AI agents to use SAGE for noisy terminal work |
| Local database | Keeps command history, compression proof, and retry context on the user's machine |
| Local proof | Keeps command and compression metrics on the user's machine |
SAGE does not auto-enable MCP. MCP is optional and manual for users who want it.
Latest pulled stats as of 2026-08-01:
| Metric | Value |
|---|---|
| SAGE telemetry command events | 27,892 |
| Tokens processed | 799.5M |
| Tokens saved | 783.7M |
| Compression rate | 98.02% |
| Estimated savings | $16,261.90 |
| Command success rate | 88.3% |
| PyPI downloads, last 7 days | 632 |
| npm downloads, last 7 days | 362 |
| GitHub clones, last 14 days | 574 |
AI coding agents burn context on repeated logs, failed test output, install noise, stack traces, and build spam. SAGE sits between the command and the agent.
| Without SAGE | With SAGE |
|---|---|
| Agent sees full noisy terminal output | Agent sees the useful summary |
| Context disappears fast | Context lasts longer |
| Repeated failures waste tokens | Errors are grouped and explained |
| Raw logs may enter prompts | Raw logs stay local |
| Hard to prove savings | SAGE records proof metrics |
| Channel | Package | Status |
|---|---|---|
| PyPI | psycgod-sage | Canonical Python package |
| npm / npx | psycgod-sage | Node launcher for the Python core |
| MCP Registry | io.github.PsYcGoD/sage | Optional/manual MCP entry |
| Glama | PsYcGoD/sage | Optional/manual hosted MCP listing |
The npm package delegates to the Python implementation so both install paths use the same local database, telemetry rules, compression, and command behavior.
sage install # Activate this machine and AI-agent instructions
sage doctor --activation # Verify activation npx -y psycgod-sage doctor --activation sage run -- # Wrap any command sage run --cwd /project -- # Explicit workspace for host integrations sage pytest # Shortcut for: sage run -- pytest sage npm test # Shortcut for: sage run -- npm test sage git status # Shortcut for: sage run -- git status sage context stats # Token savings summary sage context report # Full compression report sage history --limit 10 # Recent command history sage explain --failed # Explain the latest failed command sage suggest --failed # Suggest the next fix sage fix --apply # Try an automatic fix sage ml setup # Optional ML V2 dependencies sage mcp install # Optional/manual MCP config sage dashboard start # Local dashboard
| Mode | Requires login? | Sends data? | What leaves the machine? |
|---|---|---|---|
| Local-only | No | No | Nothing |
| Debug telemetry | Optional | Opt-in only | Redacted diagnostic summaries |
SAGE is designed to keep prompts, source code, credentials, raw command output, and project files local unless the user deliberately enables a feature that requires sending data.
| Limitation | What To Do |
|---|---|
| Already-open AI-agent sessions may not reload new instructions | Restart Claude/Codex/Cursor/Windsurf/OpenCode after sage install |
| Locked-down host apps can disable shell tools | SAGE cannot enable tools the host application has blocked |
| A host starts its shell in the wrong folder | Pass sage run --cwd -- or set SAGE_WORKSPACE_CWD |
| npm/PyPI installs cannot safely auto-run activation | Run sage install once after package install |
| MCP can disconnect in some stdio agent sessions | Use normal sage run -- by default; enable MCP manually only if needed |
| Package installs are passive by design | Real activation starts with sage install |
| Flow | Preview |
|---|---|
| PyPI install | |
| npm install | |
sage run -- | |
| CLI run |
MIT. See LICENSE.