M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBabysitter MCP ServerEnforce obedience on agentic workforces and manage extremely complex workflows through deterministic, hallucination-free self-orchestration.Context7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS40 / 100 · D80 / 100 · B
Reliability6 / 2014 / 20
Security and permissions7 / 2016 / 20
Maintenance9 / 2017 / 20
Documentation11 / 2015 / 20
Setup experience7 / 2018 / 20
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
  • Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
  • Scenarios wanting zero-config documentation lookup
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)
  • Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
  • Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
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
  • Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
  • Read-only documentation lookup — no code execution or local filesystem access involved
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
  • The free tier has limited quota — high-frequency use may hit rate limits
  • Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
Supported clientsClaude Code, Codex, Cursor, Gemini CLI, GitHub CopilotClaude Code, VS Code, Cursor, Cline, Amp
Tools02