ralph-loop-mcp
Automates a three-phase development workflow: planning, spec generation, and iterative task execution with verification.
README
Ralph Loop MCP (Node + TypeScript)
This MCP server turns the repo's .ralph/ folder into a 3-phase workflow:
- Phase 1: Create or refine plan documents under
.github/plans/. Phase 1 produces plan files only. - Phase 2: Generate/refine specs under
.ralph/specs/**and tasks in.ralph/fix_plan.md. - Phase 3: Iterate one task at a time with strict verification (npm run ci + npm run test:e2e).
See docs/DESIGN.md for architecture and positioning.
Phase 1 generator script
ralph.generate_phase1 bootstraps .ralph/phase1.sh and seeds .github/plans/project-plan.md when missing.
The generated Phase 1 session is intentionally constrained to planning output only:
-
It writes plan documents only under
.github/plans/ -
It does not create
.ralph/specs/** -
It does not create
.ralph/fix_plan.mdtask items -
Run directly:
bash ./.ralph/phase1.sh -
Run via MCP tool:
ralph.generate_phase1
Phase 2 generator script
ralph.generate_phase2 scaffolds .ralph/phase2.sh and creates the baseline Phase 2 artifacts:
-
.ralph/specs/*.md -
.ralph/fix_plan.md -
.ralph/config.json -
.ralph/logs/progress.txt -
.ralph/logs/learnings.md -
Run directly:
bash ./.ralph/phase2.sh -
Run via MCP tool:
ralph.generate_phase2
ralph.generate_phase2 performs a lightweight schema validation of .ralph/config.json.
If the file exists and is invalid, the tool reports validation errors without executing the script.
Phase 3 generator script
ralph.generate_phase3 scaffolds .ralph/phase3.sh and creates the Phase 3 prompt files.
It fails with a clear error if .ralph/fix_plan.md does not yet exist.
When the fix plan has fewer than five unchecked active tasks, it seeds Phase 2 planning items as checkboxes automatically.
Artifacts created:
-
.ralph/phase3.sh -
.ralph/phase3-plan-prompt.md -
.ralph/phase3-dev-prompt.md -
.ralph/phase3-dev-signoff-prompt.md -
.ralph/phase3-qa-prompt.md -
.ralph/phase3-qa-close-prompt.md -
.ralph/logs/phase3-feedback.md -
Run directly:
bash ./.ralph/phase3.sh -
Run via MCP tool:
ralph.generate_phase3
Prerequisites
- Node.js 20 or later
- npm
- Build the package before running or testing (see Build section below)
Install
Standalone (this repo cloned directly as the package root):
npm install
Nested (package embedded under a parent monorepo, e.g. at ./mcp/ralph_loop_mcp):
npm install --prefix ./mcp/ralph_loop_mcp
Build
Standalone:
npm run build
Nested:
npm run --prefix ./mcp/ralph_loop_mcp build
Run (stdio)
Standalone:
node dist/index.js
Nested:
node ./mcp/ralph_loop_mcp/dist/index.js
VS Code MCP registration
Set cwd to the target project -- the repo whose .ralph/ folder the server will manage. This is typically the project you are actively developing, not the directory where this MCP package lives.
Example configuration for a standalone clone (open the target project folder in VS Code so ${workspaceFolder} resolves to it):
{
"mcpServers": {
"ralph-loop": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "${workspaceFolder}"
}
}
}
Example for a nested layout where the package lives at ./mcp/ralph_loop_mcp inside the target project:
{
"mcpServers": {
"ralph-loop": {
"command": "node",
"args": ["./mcp/ralph_loop_mcp/dist/index.js"],
"cwd": "${workspaceFolder}"
}
}
}
If VS Code reports ${workspaceFolder} cannot be resolved, open the repository with File -> Open Folder..., or set cwd to an absolute path pointing at the target project root.
Verification prereqs
ralph.run_verification runs npm run ci followed by npm run test:e2e on the target repo (the project under cwd). Both scripts must be defined in that repo's package.json, or the tool will reject them by design.
To extend the allowlist for additional scripts, add an allowedNpmScripts array to .ralph/config.json in the target repo:
{
"allowedNpmScripts": ["lint", "type-check"]
}
Conventions
.ralph/fix_plan.mdis the task source of truth.- Blocked tasks live under a dedicated heading:
## Blocked(or## Blocked Tasks). - Phase 1 planning documents live under
.github/plans/. - Phase 2 generator script lives at
.ralph/phase2.shand is auto-created byralph.generate_phase2when absent. - Phase 3 generator script lives at
.ralph/phase3.shand is auto-created byralph.generate_phase3when absent.
Dev tests
Standalone:
npm test
Nested:
npm run --prefix ./mcp/ralph_loop_mcp test
Note: Run
npm run buildbefore running tests for the first time sodist/index.jsexists for integration tests.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。