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.

DimensionInkeep AgentsBuild AI Agents with a No-Code Visual Builder or TypeScript SDK, with full 2-way sync.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 permissions11 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Teams where technical and non-technical members collaborate on agents in one platform
  • Teams needing a no-code visual builder and TypeScript SDK with 2-way sync
  • Teams needing a multi-agent architecture
  • Teams wanting to self-host and deploy on their own infrastructure
  • Developers needing MCP tools with credential management and choice of LLM provider
  • 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 who cannot accept a source-available license or competitive-use restrictions (ELv2 and Inkeep's Supplemental Terms)
  • Users wanting a simple, ready-to-use client configuration (the source provides no client config example)
  • Users unwilling to deploy or maintain infrastructure themselves (self-hosting requires own deployment)
  • Users not intending to use TypeScript or the no-code interface
  • 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
  • Configuration of agents, sub agents, MCP servers, credentials, and projects (via agents-api)
  • Credential management for MCP tools
  • Access to the configured LLM providers
  • Running on your own infrastructure when self-hosted (Vercel or Docker)
  • Observability data emitted via OpenTelemetry when tracing is used
  • 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
  • ELv2 is a source-available license subject to Inkeep's Supplemental Terms, which restrict certain competitive uses
  • MCP tool credentials, if mishandled, could expose sensitive information
  • Agents can perform write operations such as updating CRMs, knowledge bases, and tickets, so mistakes can affect production data
  • Self-hosted deployment means you bear security and operational responsibility
  • LLM provider data handling and costs depend on the chosen provider
  • 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 Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00