Schema | dev-loop-mcp

dev-loop-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`DEV_LOOP_ROOT`	No	Project root directory (defaults to cwd)
`ANTHROPIC_API_KEY`	Yes	Your Anthropic API key

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
start_loopA	Start a new TDD development loop. Returns an instruction telling you what to do first. Keep calling advance_loop after each step until the loop reaches DONE or FAILED. Phases: INIT → DECOMPOSE → TDD_LOOP → BUILD → DEPLOY → INTEG_TEST → INTEG_FIX → QUALITY_REVIEW → CLEAN_TREE_CHECK → PUSH_AND_PR.
start_debug_loopC	Start a debug loop from a symptom description. Returns an instruction telling you to diagnose root causes as ranked TDD tasks, then proceeds through the standard TDD pipeline. The PR body will include a diagnosis writeup.
advance_loopA	Report the outcome of the last instruction and get the next one. Call this after completing each phase step. The loop persists state between calls.
loop_statusB	Get the current status of the loop: phase, branch, task list, failure reason, or PR URL.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soynog/dev-loop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server