ToolsMCP
datadog
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- us-all (GitHub)
- Prerequisites
- Install @us-all/datadog-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.21.1 · updated
- Official links
Publisher’s description
Datadog MCP — 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.21.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- us-all (GitHub)
- Version observed
- 1.21.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.us-all%2Fdatadog/versions/1.21.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Investigate errors and incidents | Publisher description mentions “datadog”, “metrics”, “logs”, “incidents”. | No connection check or task run. Capability is as described by the publisher. | Rule observability matched: “datadog”, “metrics”, “logs”, “incidents”. Rule observability. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@us-all/datadog-mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.us-all/datadog
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.