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.

DimensionYALCOpen-source, AI-native GTM operating system. CLI-first.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS50 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • SMB B2B teams looking for an open-source, customizable GTM automation tool.
  • Developers who use Claude Code and want to integrate GTM workflows.
  • Operations teams that prefer CLI or MCP-controlled end-to-end campaigns.
  • 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
  • Enterprise users needing a fully managed, GUI-driven GTM platform.
  • Teams requiring a pre-built, maintained MCP server rather than a CLI tool.
  • Users seeking official support from a CRM/ESP or similar vendor.
  • 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
  • Access external APIs (Unipile, Crustdata, Firecrawl, Notion, FullEnrich, Instantly, Anthropic, etc.)
  • Read/write local filesystem (`~/.gtm-os/`, `./data/`)
  • Start a local dashboard server (port 3847) and open browser
  • Run background agents on your system (launchd)
  • 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
  • May send unsolicited messages if misconfigured, potentially violating platform policies.
  • API keys stored locally in `~/.gtm-os/.env`; exposure could lead to unauthorized usage.
  • Automated messages may not always align with brand voice; human review is recommended.
  • Relies on multiple external services that may change APIs or incur costs.
  • 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
Tools200