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 MCPGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS62 / 100 · C76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions15 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience14 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1015