Schema | Datadog MCP Server

Datadog MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`DATADOG_SITE`	No	The Datadog site (e.g. datadoghq.eu)
`DATADOG_API_KEY`	Yes	Your Datadog API key
`DATADOG_APP_KEY`	Yes	Your 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`	{}

Functions exposed to the LLM to take actions

Name	Description
list_incidentsC	Get incidents from Datadog
get_incidentC	Get an incident from Datadog
query_metricsC	Query timeseries points of metrics from Datadog
list_metricsC	List active metric names from Datadog
get_monitorsC	Get monitors status from Datadog
list_dashboardsC	Get list of dashboards from Datadog
get_dashboardC	Get a dashboard from Datadog
list_spansC	Get a list of spans matching a search query
get_rum_applicationsB	Get all RUM applications in the organization
get_rum_eventsC	Search and retrieve RUM events from Datadog
get_rum_grouped_event_countC	Search, group and count RUM events by a specified dimension
get_rum_page_performanceC	Get page (view) performance metrics from RUM data
get_rum_page_waterfallB	Retrieve RUM page (view) waterfall data filtered by application name and session ID

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/datgfg/mcp-server-datadog'

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