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.

DimensionLogClaw MCP ServerConnect AI coding tools to LogClaw incidents, logs, and anomaly detectionsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS56 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • SRE and development teams already running LogClaw or using its cloud service
  • Engineers who want incident and log data directly in Claude Code, Cursor, or Windsurf
  • 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 do not use the LogClaw platform
  • Anyone without a valid LOGCLAW_API_KEY (lc_proj_ prefix)
  • 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 a valid LogClaw project API key (lc_proj_ prefix)
  • Network access to the LogClaw auth proxy endpoint (default https://ticket.logclaw.ai)
  • 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 key leakage could expose project incident and log data; secure environment variables accordingly
  • Logs exposed to AI tools may contain sensitive operational information
  • Depends on remote endpoint availability; the self-hosted local stack runs single-tenant with AI RCA disabled by default
  • 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, Cursor, WindsurfClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00