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.

DimensionDatadog MCP ServerRead-only access to Datadog monitoring data via MCPMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS62 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions15 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Ops and SRE teams using Claude Desktop who need read-only access to Datadog data
  • Developers who want monitors, logs, and metrics queries inside LLM workflows
  • Teams practicing least privilege who can scope their Application Keys
  • 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
  • Scenarios requiring write operations to Datadog (creating/modifying monitors, muting, etc.) — the server offers read-only tools only
  • Users without a Datadog account, API key, and Application key
  • Those requiring official Datadog support — this is a community project, not official
  • 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
  • DD_API_KEY: Datadog API key
  • DD_APP_KEY: Datadog Application key, recommended scopes per feature: monitors_read, dashboards_read, metrics_read, events_read, logs_read_data, incident_read
  • Application Keys without explicit scopes inherit all permissions of the creating user
  • 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
  • Leaked API or Application keys expose organizational monitoring and log data
  • Application Keys without scopes carry the creator's full permissions, violating least privilege
  • Third-party community project, not audited by Datadog
  • Logs and metrics may contain sensitive business data entering LLM context — consider compliance implications
  • 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
Tools100