ralph-loop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ralph.generate_phase1A | Set up Phase 1: creates .ralph/phase1.sh and .ralph/phase1-prd-prompt.md, seeds a draft .github/plans/project-plan.md if missing. Run bash .ralph/phase1.sh to normalize the source plan into the canonical PRD at .ralph/prd.md via ralph.write_prd. Configure phase1.sourcePlan in .ralph/config.json (default .github/plans/project-plan.md). When the PRD is ready, run ralph.generate_phase2. |
| ralph.write_planA | Write or update a planning document under .github/plans/. Use for draft plans before Phase 1 PRD normalization, or auxiliary planning docs. |
| ralph.write_prdA | Write or replace the canonical product requirements document at .ralph/prd.md. Used by the Phase 1 Copilot session only. |
| ralph.read_stateA | Read .ralph state: config, parsed tasks, spec index, PRD tail, and log tails. Call at the start of Phase 2/3 iterations. |
| ralph.list_filesA | List files and directories one level deep under a repo-relative path. Use this during Phase 2 exploration to discover source files, then read them with ralph.read_file. |
| ralph.read_fileA | Read any text file inside the repo by its repo-relative path. Use this during Phase 2 to explore source code and inform spec and fix-plan authoring. |
| ralph.write_epic_planB | Write/update the canonical .ralph/epic_plan.md file. |
| ralph.upsert_specA | Write/update a spec file under .ralph/specs/**. Call this iteratively during Phase 2 as you explore source files and refine your understanding. |
| ralph.replace_fix_planA | Replace .ralph/fix_plan.md, optionally preserving completed items from the previous file. Phase 2/3: use preserveCompleted:true when refining. You may add |
| ralph.next_taskA | Return the next unchecked active task from .ralph/fix_plan.md (ignores blocked tasks). |
| ralph.set_task_statusA | Check/uncheck a task in .ralph/fix_plan.md by text or taskId. In Phase 3, only the QA-close persona should call this with checked:true after Dev agrees sign-off. |
| ralph.block_taskC | Move an active task into the dedicated Blocked section with a short reason. |
| ralph.unblock_taskB | Move a blocked task back into the active task list (unchecked by default). |
| ralph.append_progressA | Append a timestamped entry to .ralph/logs/progress.txt. |
| ralph.append_learningB | Append a new section to .ralph/logs/learnings.md. |
| ralph.generate_phase2A | Set up Phase 2: .ralph/phase2.sh (planning persona + worker loop), config.json with defaults, phase2-planner-prompt.md, phase2-worker-prompt.md, specs/, logs/. Phase 2 reads paths.projectPlan (default .ralph/prd.md). Ensure .ralph/prd.md exists first. Run bash .ralph/phase2.sh after setup. |
| ralph.generate_phase3A | Set up Phase 3: .ralph/phase3.sh — Plan, Dev, QA personas, Dev/QA consensus sign-off, then QA close marks tasks done. Prompt files: phase3-plan-prompt.md, phase3-dev-prompt.md, phase3-qa-prompt.md, sign-off prompts. Requires .ralph/fix_plan.md. Run bash .ralph/phase3.sh. |
| ralph.run_verificationA | Run strict verification gate: npm run ci, then npm run test:e2e (stop on first failure). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools map to a distinct file, phase, or action; the write_ family is separated by documented destinations (plans, PRD, epic, specs, fix_plan). read_state vs read_file and the multiple generate_phase tools have slight conceptual overlap, but the descriptions clearly indicate when each should be used.
All tools share the ralph. prefix and use lowercase_snake_case with a mostly verb_noun pattern (write_plan, block_task, run_verif). Minor deviations such as next_task (lacking a verb) and write_prd (abbreviated object) keep it from being perfectly consistent.
At 18 tools, the set is slightly above the ideal 3-15 range, but the multi-phase workflow (setup, planning, spec writing, task tracking, logging, verification) justifies the breadth. Each tool serves a distinct step in the ralph loop, so the count feels reasonable rather than bloated.
The toolset covers the full ralph loop lifecycle: phase setup, PRD/plan/spec/fix-plan authoring, task state transitions, logging, and verification. Minor gaps exist—no dedicated raw fix_plan reader and no cleanup/rollback tool—but agents can work around these via read_state and overwrite capabilities.