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.

DimensionBuildkite MCP ServerOfficial Buildkite MCP server exposing Buildkite data to AI tooling.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Development teams using Buildkite for CI/CD
  • Teams wanting to integrate AI tools into their development workflow
  • DevOps engineers needing quick access to build information
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users not using Buildkite
  • Those needing a graphical interface (MCP server does not provide UI)
  • Scenarios requiring non-official data sources
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires BUILDKITE_API_TOKEN to authenticate with Buildkite API
  • Token permissions determine the scope of accessible data (e.g., read pipelines, builds, logs)
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • API token leakage: keep token confidential and only pass in secure environments
  • Job logs may contain sensitive information; ensure caller permissions are correct
  • In HTTP mode, if header passthrough is configured, ensure the reverse proxy authenticates properly
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools70