← Back to directory
B

Babysitter MCP Server

Community
Enforce obedience on agentic workforces and manage extremely complex workflows through deterministic, hallucination-free self-orchestration.
GitHub source repository ↗
★ 1.8k Stars Category · Dev Tools Very popular
40FMRS · D

Babysitter is an MIT-licensed orchestration tool whose central claim is enforcement over agent behavior: processes written in JavaScript are the sole authority, every step ends in a mandatory stop, gates block progression, breakpoints require human approval, and all decisions are journaled and replayable. v6 adds an Adapters runtime so the same processes run across the 12 harnesses in its install matrix. The README documents multiple npm packages, marketplace plugin installs, and a built-in internal harness. It suits teams that need strong process control, auditability, and resumability, but it writes to a state directory, acts on the workspace according to each process, and blueprints can perform broad installation actions. MCP-related capability (for example genty start-server --transport stdio) is inferred from the supplied README; the source provides no verifiable MCP tool list or client config example, so those fields are left empty.

Reliability
6/20
Security and permissions
7/20
Maintenance
9/20
Documentation
11/20
Setup experience
7/20
Read the FMRS scoring method →

Babysitter is an MIT-licensed tool for agentic orchestration whose stated purpose is to enforce obedience on agentic workforces and let them manage extremely complex workflows through deterministic, hallucination-free self-orchestration. Workflows are defined in JavaScript code (a process): the orchestrator can only do what that code permits, every step ends with a mandatory stop, quality gates block progression, breakpoints require human approval, and every decision is recorded in an immutable, deterministically replayable event-sourced journal. As of v6 it is harness-agnostic via its Adapters runtime, so the same processes run across the 12 AI coding harnesses in its install matrix. Install surfaces include the npm packages @a5c-ai/babysitter (main CLI), @a5c-ai/adapters-cli (host-side adapters CLI, Node >= 22.13.0), @a5c-ai/babysitter-sdk (public SDK/library), and @a5c-ai/genty-platform (optional runtime CLI with call, resume, plan, start-server, tui), plus per-harness plugins. The README also documents a built-in internal harness that runs processes programmatically without any external AI coding agent and can delegate tasks to discovered harness CLIs, a 4-layer token compression subsystem, and a blueprint marketplace of natural-language instructions or deterministic JS processes. The repository also contains an adjacent kip-sdk memory substrate package.

Setup

  1. Ensure Node.js >= 20.0.0 (22.x LTS recommended); the host-side adapters CLI requires Node >= 22.13.0.
  2. Install the main CLI: npm install -g @a5c-ai/babysitter.
  3. To drive a harness from your shell, install the host-side CLI: npm install -g @a5c-ai/adapters-cli, then run adapters doctor.
  4. Install the Babysitter plugin for your harness, e.g. Claude Code: claude plugin marketplace add a5c-ai/babysitter-claude, then claude plugin install --scope user [email protected], restart, and verify "babysit" appears via /skills.
  5. Alternatively use the scriptable installer: babysitter harness:install-plugin <harness> (cursor, gemini-cli, github-copilot, pi, hermes, oh-my-pi, opencode, openclaw).
  6. Run one-time setup: /babysitter:user-install, /babysitter:project-install, then verify with /babysitter:doctor.
  7. For runtime orchestration commands, optionally install @a5c-ai/genty-platform and use genty.

Fit and risk

Best for

  • Teams that need enforced process control and an auditable journal
  • Users working across multiple AI coding harnesses who want one process definition
  • Complex agentic workflows that must be replayable, resumable, and gated by humans
  • Engineering teams that want headless orchestration in CI/CD without an external AI agent

Not for

  • Users who only need one-off chat or single-step code generation
  • Environments where installing Node.js or running external CLIs is not possible
  • Teams wanting fully autonomous automation that cannot tolerate mandatory stops and approvals
  • Users who want to consume the kip-sdk package from npm (it is private/0.0.1, unpublished)

Required permissions

  • Write access to the run state directory (default ~/.a5c/runs/, with repo-local .a5c/runs/ compatibility reads)
  • Create or modify files in the project directory, as determined by the process code being run
  • Perform anything an AI agent can do inside a process, including installing npm packages, generating CI/CD configuration, and setting up git hooks
  • Invoke discovered harness CLIs and external commands during process execution
  • Read and modify .a5c/compression.config.json to configure compression layers

Risks and side effects

  • Process code is the authority, so a poorly written process can cause unintended file changes or command execution
  • Quality-gated processes may iterate repeatedly until gates pass, consuming significant tokens and time
  • Plugin installation uses user scope, affecting all sessions for that user
  • Blueprints can install npm packages, modify linter rules, and write CI configuration, so their instructions should be reviewed before approval
  • The README states babysitter harness:install and harness:discover are deprecated, so older commands may stop working

Troubleshooting

  1. Run /babysitter:doctor or genty doctor --run-id <runId> to diagnose run health
  2. After installing the Claude Code plugin, restart and check that "babysit" appears via /skills
  3. If the adapters CLI fails, confirm Node is >= 22.13.0
  4. Resume an interrupted run with /babysitter:resume or genty resume --run-id <runId>
  5. If context usage is too high, inspect settings with babysitter compression:config or disable a layer with babysitter compression:toggle <layer> off
  6. Use --harness internal when no external AI agent is available

Use cases

Implement features with TDD while enforcing quality gates
Run processes headlessly in CI/CD or scripts via the internal harness
Orchestrate multi-agent workflows by delegating subagent tasks across harnesses
Insert human approval breakpoints at critical steps
Resume an interrupted run deterministically from the journal
Use blueprints to set up security, testing, deployment, and CI/CD configuration

Supported clients

Claude CodeFull support
Codex CLIFull support
CursorPartial support
Gemini CLIPartial support
GitHub CopilotPartial support