Schema | datadog-logs-mcp

datadog-logs-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`DD_SITE`	No	Datadog site (default: datadoghq.com). Use datadoghq.eu, us3.datadoghq.com, us5.datadoghq.com, etc.	datadoghq.com
`DD_API_KEY`	Yes	Datadog API key
`DD_APP_KEY`	Yes	Datadog Application key

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
search_logsA	Search Datadog logs using the log search syntax. Returns matching log entries with their attributes, timestamps, and metadata.
get_logA	Retrieve a specific Datadog log entry by its unique ID. Requires the approximate timestamp of the log to narrow the search.
aggregate_logsA	Aggregate Datadog logs to compute metrics like count, avg, sum, min, max, percentiles. Supports group-by for breakdowns.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bgrgndzz/datadog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server