ralph-wiggum-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RALPH_AUTO_COMMIT | No | Enable auto-commit by default | false |
| RALPH_HISTORY_LIMIT | No | Maximum history entries | 100 |
| RALPH_MAX_ITERATIONS | No | Default maximum iterations | 50 |
| RALPH_STAGNATION_THRESHOLD | No | Iterations before stagnation warning | 5 |
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_loopB | Start a Ralph Wiggum iterative development loop. Ralph is a development methodology based on continuous AI agent loops. The technique creates a self-referential feedback loop where the same prompt is fed back repeatedly, allowing the AI to iteratively improve its work until completion. NEW FEATURES:
Use ralph_list_templates to see available templates. |
| ralph_iterateA | Process the next iteration of a Ralph loop with enhanced tracking. After completing work on the current iteration, call this tool with your output and optional metadata to:
Enhanced features:
|
| ralph_cancelA | Cancel the active Ralph loop. Stops the current Ralph loop and removes all state. Use this when you want to manually stop the loop before completion. |
| ralph_statusA | Get the current status of the Ralph loop with progress insights. Shows:
|
| ralph_historyB | Get detailed iteration history report. Shows a comprehensive history of all iterations including:
|
| ralph_list_templatesC | List all available Ralph loop templates. Templates are pre-built prompts and configurations for common tasks:
Each template includes suggested settings and external tools. |
| ralph_get_templateB | Get details of a specific template. Returns the full template configuration including:
|
| ralph_git_statusA | Get git status and diff summary. Shows:
|
| ralph_git_commitA | Create a git commit for the current iteration. Use this to manually create a commit with a custom message. If auto_commit is enabled, commits are created automatically. |
| ralph_git_contextC | Get context from recent Ralph commits. Shows recent Ralph iteration commits from git history, providing context about what was done in previous iterations. |
| ralph_run_toolsA | Run external tool presets (test runners, linters, etc.). Available presets:
Use ralph_detect_tools to see which presets are available for your project. |
| ralph_detect_toolsA | Detect which tool presets are available for the current project. Analyzes the project structure and suggests relevant tool presets (e.g., if package.json exists, suggests javascript-test and javascript-lint). |
| ralph_list_toolsA | List all available external tool presets. Shows all available tool presets with descriptions, regardless of whether they're applicable to the current project. |
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 13 tools
Most tools have clearly distinct purposes, with only minor potential confusion between ralph_git_status and ralph_status. The git-focused tools (git_commit, git_context, git_status) are well-separated from the core loop tools (loop, iterate, cancel, status). However, ralph_detect_tools and ralph_list_tools could be slightly ambiguous about whether they show available vs. applicable tools.
All tools follow a consistent 'ralph_' prefix with snake_case naming throughout. The naming pattern is highly predictable: ralph_verb_noun or ralph_noun_verb where the second part clearly indicates the action or resource. This consistency makes the tool set easy to navigate and understand.
13 tools is an appropriate number for a comprehensive development loop management system. The count covers all essential aspects: loop control (loop, iterate, cancel, status), template management (list_templates, get_template), tool integration (list_tools, detect_tools, run_tools), git operations (git_commit, git_context, git_status), and history tracking (history). Each tool serves a distinct purpose within the domain.
The tool surface provides complete coverage for the Ralph development loop methodology. It includes all necessary operations: starting and controlling loops (loop, iterate, cancel, status), managing templates (list, get), integrating external tools (detect, list, run), tracking changes through git (commit, context, status), and accessing history. There are no apparent gaps that would prevent agents from implementing the full workflow.