Datadog Logs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 5000 |
| DD_API_KEY | Yes | Your Datadog API key (required) | |
| DD_APPLICATION_KEY | Yes | Your Datadog application key (required) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsC | Search Datadog logs with a query and time range |
| search_cloudbeds_pmsC | Search Cloudbeds PMS API for reservations with rate details |
| search_clickhouseC | Query Clickhouse database (currently unimplemented) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose targeting different data sources: Clickhouse database queries, Cloudbeds PMS API for reservations, and Datadog logs search. There is no overlap in functionality or ambiguity about which tool to use for each specific task.
All three tools follow a consistent verb_noun pattern with 'search_' prefix followed by the target resource (clickhouse, cloudbeds_pms, logs). The naming is perfectly uniform and predictable across the entire tool set.
With only 3 tools, the server feels somewhat thin for a 'Datadog Logs MCP Server' that also includes non-Datadog tools. While the tools are well-defined, the scope appears broader than just logs, and the count may be insufficient for comprehensive coverage of the implied domains.
For a server named 'Datadog Logs', having only one Datadog-specific tool (search_logs) with two unrelated tools creates significant gaps. The Clickhouse tool is unimplemented, and the Cloudbeds tool seems out of scope, leaving the core Datadog functionality incomplete and fragmented.