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.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS40 / 100 · D76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions7 / 2014 / 20
Maintenance9 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience7 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Codex, Cursor, Gemini CLI, GitHub CopilotClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015