A
licenseB
qualityC
maintenanceA Model Context Protocol server that enables AI assistants to communicate with each other using Inter-Process Communication, featuring natural language commands and cross-platform compatibility.
9
133
MIT
Datadog MCP Server
by brukhabtu
Related Servers
Alternatives to Datadog MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA lightweight Model Context Protocol server that enables creating, managing, and querying model contexts with integrated Datadog metrics and monitoring.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.46 npm2MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.2-
- FlicenseCqualityDmaintenanceA collection of Model Context Protocol servers providing advanced capabilities for AI assistants including professional accuracy enforcement, tool safety protocols, user preference management, and intelligent context monitoring.5-
- AlicenseAqualityDmaintenanceA template for building Model Context Protocol servers that allow AI assistants to interact with custom data and services through queryable resources and specialized tools.6MIT
TDQS
B3/5.0
Scored across 72 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific Datadog resources (e.g., GetApmRetentionFilter vs. GetLogsArchive), with clear descriptions that help differentiate them. However, some overlap exists in list operations across different resource types (e.g., ListAPIKeys, ListApplicationKeys) which could cause minor confusion, though their names and descriptions generally clarify the target resource.
Naming Consistency5/5
Tool names follow a highly consistent pattern throughout: all use PascalCase with clear verb-noun combinations (e.g., GetIncident, ListSecurityMonitoringRules, ConvertExistingSecurityMonitoringRule). The naming convention is predictable and uniform across all 72 tools, making them easily readable and organized.
Tool Count2/5
With 72 tools, the count is excessive for a single server, making it overwhelming for agents to navigate and understand the scope. While Datadog is a broad platform, this many tools suggests poor scoping and could lead to confusion, as typical well-scoped servers have 3-15 tools. The high count indicates a lack of curation or aggregation.
Completeness4/5
The tool set provides extensive coverage of Datadog's API surface, including CRUD operations for incidents, logs, metrics, security monitoring, and more, with few obvious gaps. However, some areas like full lifecycle management for all resources (e.g., update/delete for certain entities) may be incomplete, but agents can generally work around this given the breadth of operations available.