irrigator
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
What it adds
Irrigator runs coding agents in parallel while keeping results, retries and spending evidence on disk. Use the CLI directly or through Claude Code, Codex and Antigravity plugins. Inspect the work and resume from your terminal.
Capability | What it gives you |
Durable execution | Saved plans, attempts and accepted artifacts that survive interruptions. |
Coding cells | One task per git worktree, with branches and objective checks to review. |
Bounded delegation | Explicit task graphs, worker concurrency and provider limits. |
Recovery decisions | Uncertain external work stays visible and is never silently replayed. |
Terminal review |
|
Related MCP server: coding-agent-mcp
Quick start
Install the stable CLI from the shared Grainulation tap:
brew tap grainulation/homebrew https://github.com/grainulation/homebrew
brew install grainulation/homebrew/irrigator
irrigator doctor
irrigator demoThe demo uses mock workers, needs no credentials and makes no model calls. Each invocation creates a fresh run directory and prints inspection commands. For your own plan, follow the first-run guide.
The stable formula installs a pinned release archive and does not need Go.
See the tap's available formulae
for the current stable version. For a development source build, use
brew install --HEAD grainulation/homebrew/irrigator.
See the Homebrew guide for supported platforms, upgrades and checks.
From source
Requires Go 1.26.7+, make and a POSIX shell. Development and CI pin Go 1.27.2.
git clone https://github.com/grainulation/irrigator.git
cd irrigator
make build
./irrigator doctor
./irrigator demoTo install from this checkout, run make install PREFIX="$HOME/.local" and add
$HOME/.local/bin to PATH. Installation copies the CLI; agent plugins and
provider tools have their own setup. CLI archives and their installation checks
are described in runtime releases.
Ask your agent to start
Give Claude Code, Codex or Antigravity this prompt from the checkout:
Read README.md and AGENTS.md in the Irrigator repository. Build ./irrigator with make build,
run ./irrigator agents and ./irrigator demo, and report the exit codes and final status lines.
Tell me which routes below this machine can run. Ask before any model-backed or paid run.Route | What it does | Needs | Cost and limits |
1. Mock demo and starter plan |
| Local CLI | No model calls or API spend |
2. Local models | Managed tasks using Ollama | CLI, Ollama and a local model | Local compute; no API spend |
3. Managed CLI profiles | Turn/helper graphs via | CLI and authenticated provider | Cost tracking by default; explicit enforced-budget profiles available |
4. Coding cells |
| CLI, git repo and an agent CLI | Per-cell timeout; Claude USD cap; Codex/agy cost unknown, no USD cap |
Real providers use your account or local compute. New managed plans track estimates without blocking when costs are unavailable; tracking thresholds warn. Enforced budgets control admission and reservations and can still be overrun by a provider. Unknown cost never means free execution. See cost tracking and enforced budgets.
Put it to work
Start with a plan, validate it, then choose a backend explicitly:
./irrigator init --out plan.json
./irrigator plan plan.json
./irrigator apply plan.json --run runs/first --backend mock
./irrigator status runs/firstUse new plan filenames and run directories. For repository changes, coding
cells accept --task ID=PROMPT and --verify ID=COMMAND; results land on local
branches for review. A verification timeout or exit 77 leaves the result uncertain, as does a
successful check that changes the worktree or Git identity. See coding cells
for setup, spending limits and recovery.
For graphs that grow during execution, choose recursive spawning or managed turns and helpers. These have separate execution rules; worker concurrency is independent of graph size.
Plugins
Install the irrigator runtime separately, then follow
agent setup for your host:
Host | Setup |
Claude Code | |
Codex | |
Antigravity | |
Other MCP hosts |
The plugins share Markdown skills and the local CLI under the host's normal execution permissions. Host integration covers installation and discovery checks; static package checks alone do not establish that a host can load or invoke a plugin.
Explore the docs
Guide | Start here for… |
Your own plan, provider selection and inspection. | |
Parallel repository tasks and verification commands. | |
Role routing, quota/reset advisories, delivery summaries and the offline benchmark. | |
Paginated captured output with redaction and capture-loss metadata. | |
Selective-file application, assembled-file checks and guarded undo. | |
Reusable graphs and artifact contracts. | |
Swarm dashboard and local review. | |
Interrupted calls, retries and execution authority. | |
Source layout, package layers and durable state. | |
The supported 1.x interfaces and saved-run formats. | |
Accounting, providers, command references and more. |
Verification and limits
The CLI supports macOS and Linux. Windows users run the Linux build inside WSL 2; native Windows is planned. Platform support records the tested configurations.
Worktrees keep concurrent checkouts apart; they are not a host sandbox. Approvals record a decision bound to a specific head and never merge changes. See SECURITY.md for the local trust model.
CI runs builds, mock workflows, race tests and package checks. Native host and live-provider acceptance are separate. Run the development gates with:
make acceptance
make lintThe verification matrix details their scope, including integration tests. Contributing covers setup and changes; choosing a tool explains the tradeoffs. See the changelog for releases and the release checklist for artifact promotion.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Git collaboration for AI agents and people: tasks, hand-offs, reviews, teams, shared memory.
AI work orchestration for plans, tasks, teams, and coding-agent dispatch.
Design, build and run teams of AI agents with checked handoffs between them.
Software factory for AI agents: issue and PR reviews, auto-fixes, stacked PRs and a merge queue.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables orchestrating multi-agent AI coding workflows with Git worktree isolation, parallel testing, and security scanning via the Model Context Protocol.-
- AlicenseAqualityBmaintenanceEnables supervising and orchestrating local coding agents like Muse and AGY through a client-agnostic MCP interface, with isolated Git worktrees, safe execution, and deterministic verification.1012 npmMIT
- AlicenseAqualityCmaintenanceEnables a planning agent to delegate research and implementation to lower-cost worker models in isolated git worktrees, monitor job progress, respond to blocked jobs, and land verified changes for review.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to spawn, parallelize, and synchronize multi-agent programming swarms through a stdio MCP interface. Provides tools for DAG-scheduled task dispatch, isolated Git worktree execution, atomic file locking, shared blackboard memory, and clean merging of completed agent work back to the main repository.1MIT