MCP Datadog E4bdc072

MCP运维云端

提供方 Gustibimo · 包名 @smithery/cli

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

Datadog MCP服务器是一个社区维护的项目,通过MCP服务器实现对Datadog API的访问,提供事件管理、监控、日志、仪表板和指标查询等功能。

一句话选型结论

按资料字段整理

MCP Datadog E4bdc072 属于运维云端类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 20 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量20暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

监控工具TypeScript本地部署事件管理日志查询指标分析可观测性

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx -y @smithery/cli install @winor30/mcp-server-datadog --client claude

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 20 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 20 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Datadog E4bdc072当前 20 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Gustibimo上游标注的维护方 Gustibimo
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@smithery/cli · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.1 KB
来自项目仓库与上游目录的原文,未做删改

Datadog MCP Server - Fork from winor30/mcp-server-datadog, enhanced with custom tools

> DISCLAIMER: This is a community-maintained project and is not officially affiliated with, endorsed by, or supported by Datadog, Inc. This MCP server utilizes the Datadog API but is developed independently as part of the Model Context Protocol ecosystem.

MCP server for the Datadog API, enabling incident management and more.

Features

  • Observability Tools: Provides a mechanism to leverage key Datadog monitoring features, such as incidents, monitors, logs, dashboards, and metrics, through the MCP server.
  • Extensible Design: Designed to easily integrate with additional Datadog APIs, allowing for seamless future feature expansion.

Tools

  1. list_incidents
  • Retrieve a list of incidents from Datadog.
  • Inputs:
    • filter (optional string): Filter parameters for incidents (e.g., status, priority).
    • pagination (optional object): Pagination details like page size/offset.
  • Returns: Array of Datadog incidents and associated metadata.
  1. get_incident
  • Retrieve detailed information about a specific Datadog incident.
  • Inputs:
    • incident_id (string): Incident ID to fetch details for.
  • Returns: Detailed incident information (title, status, timestamps, etc.).
  1. get_monitors
  • Fetch the status of Datadog monitors.
  • Inputs:
    • groupStates (optional array): States to filter (e.g., alert, warn, no data, ok).
    • name (optional string): Filter by name.
    • tags (optional array): Filter by tags.
  • Returns: Monitors data and a summary of their statuses.
  1. get_logs
  • Search and retrieve logs from Datadog.
  • Inputs:
    • query (string): Datadog logs query string.
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
    • limit (optional number): Maximum number of logs to return (defaults to 100).
  • Returns: Array of matching logs.
  1. list_dashboards
  • Get a list of dashboards from Datadog.
  • Inputs:
    • name (optional string): Filter dashboards by name.
    • tags (optional array): Filter dashboards by tags.
  • Returns: Array of dashboards with URL references.
  1. get_dashboard
  • Retrieve a specific dashboard from Datadog.
  • Inputs:
    • dashboard_id (string): ID of the dashboard to fetch.
  • Returns: Dashboard details including title, widgets, etc.
  1. query_metrics
  • Retrieve metrics data from Datadog.
  • Inputs:
    • query (string): Metrics query string.
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
  • Returns: Metrics data for the queried timeframe.
  1. list_traces
  • Retrieve a list of APM traces from Datadog.
  • Inputs:
    • query (string): Datadog APM trace query string.
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
    • limit (optional number): Maximum number of traces to return (defaults to 100).
    • sort (optional string): Sort order for traces (defaults to '-timestamp').
    • service (optional string): Filter by service name.
    • operation (optional string): Filter by operation name.
  • Returns: Array of matching traces from Datadog APM.
  1. list_hosts
  • Get list of hosts from Datadog.
  • Inputs:
    • filter (optional string): Filter string for search results.
    • sort_field (optional string): Field to sort hosts by.
    • sort_dir (optional string): Sort direction (asc/desc).
    • start (optional number): Starting offset for pagination.
    • count (optional number): Max number of hosts to return (max: 1000).
    • from (optional number): Search hosts from this UNIX timestamp.
    • include_muted_hosts_data (optional boolean): Include muted hosts status and expiry.
    • include_hosts_metadata (optional boolean): Include host metadata (version, platform, etc).
  • Returns: Array of hosts with details including name, ID, aliases, apps, mute status, and more.
  1. get_active_hosts_count

    • Get the total number of active hosts in Datadog.
    • Inputs:
    • from (optional number): Number of seconds from which you want to get total number of active hosts (defaults to 2h).
    • Returns: Count of total active and up hosts.
  2. mute_host

    • Mute a host in Datadog.
    • Inputs:
    • hostname (string): The name of the host to mute.
    • message (optional string): Message to associate with the muting of this host.
    • end (optional number): POSIX timestamp for when the mute should end.
    • override (optional boolean): If true and the host is already muted, replaces existing end time.
    • Returns: Success status and confirmation message.
  3. unmute_host

    • Unmute a host in Datadog.
    • Inputs:
    • hostname (string): The name of the host to unmute.
    • Returns: Success status and confirmation message.
  4. list_downtimes

    • List scheduled downtimes from Datadog.
    • Inputs:
    • currentOnly (optional boolean): Return only currently active downtimes when true.
    • monitorId (optional number): Filter by monitor ID.
    • Returns: Array of scheduled downtimes with details including scope, monitor information, and schedule.
  5. schedule_downtime

    • Schedule a downtime in Datadog.
    • Inputs:
    • scope (string): Scope to apply downtime to (e.g. 'host:my-host').
    • start (optional number): UNIX timestamp for the start of the downtime.
    • end (optional number): UNIX timestamp for the end of the downtime.
    • message (optional string): A message to include with the downtime.
    • timezone (optional string): The timezone for the downtime (e.g. 'UTC', 'America/New_York').
    • monitorId (optional number): The ID of the monitor to mute.
    • monitorTags (optional array): A list of monitor tags for filtering.
    • recurrence (optional object): Recurrence settings for the downtime.
      • type (string): Recurrence type ('days', 'weeks', 'months', 'years').
      • period (number): How often to repeat (must be >= 1).
      • weekDays (optional array): Days of the week for weekly recurrence.
      • until (optional number): UNIX timestamp for when the recurrence ends.
    • Returns: Scheduled downtime details including ID and active status.
  6. cancel_downtime

    • Cancel a scheduled downtime in Datadog.
    • Inputs:
    • downtimeId (number): The ID of the downtime to cancel.
    • Returns: Confirmation of downtime cancellation.
  7. get_rum_applications

    • Get all RUM applications in the organization.
    • Inputs: None.
    • Returns: List of RUM applications.
  8. get_rum_events

    • Search and retrieve RUM events from Datadog.
    • Inputs:
    • query (string): Datadog RUM query string.
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
    • limit (optional number): Maximum number of events to return (default: 100).
    • Returns: Array of RUM events.
  9. get_rum_grouped_event_count

    • Search, group and count RUM events by a specified dimension.
    • Inputs:
    • query (optional string): Additional query filter for RUM search (default: "*").
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
    • groupBy (optional string): Dimension to group results by (default: "application.name").
    • Returns: Grouped event counts.
  10. get_rum_page_performance

    • Get page (view) performance metrics from RUM data.
    • Inputs:
    • query (optional string): Additional query filter for RUM search (default: "*").
    • from (number): Start time in epoch seconds.
    • to (number): End time in epoch seconds.
    • metricNames (array of strings): Array of metric names to retrieve (e.g., 'view.load_time', 'view.first_contentful_paint').
    • Returns: Performance metrics including average, min, max, and count for each metric.
  11. get_rum_page_waterfall

    • Retrieve RUM page (view) waterfall data filtered by application name and session ID.
    • Inputs:
    • applicationName (string): Application name to filter events.
    • sessionId (string): Session ID to filter events.
    • Returns: Waterfall data for the specified application and session.

Setup

Datadog Credentials

You need valid Datadog API credentials to use this MCP server:

  • DATADOG_API_KEY: Your Datadog API key
  • DATADOG_APP_KEY: Your Datadog Application key
  • DATADOG_SITE (optional): The Datadog site (e.g. datadoghq.eu)
  • DATADOG_SUBDOMAIN (optional): The Datadog subdomain (e.g. .datadoghq.com)

Export them in your environment before running the server:```bash
export DATADOG_API_KEY="your_api_key"
export DATADOG_APP_KEY="your_app_key"
export DATADOG_SITE="your_datadog_site" # Optional
export DATADOG_SUBDOMAIN="your_datadog_subdomain" # Optional


## Installation

### Installing via Smithery

To install Datadog MCP Server for Claude Desktop automatically via Smithery:```bash
npx -y @smithery/cli install @winor30/mcp-server-datadog --client claude

Manual Installation```bash

pnpm install
pnpm build
pnpm watch # for development with auto-rebuild


## Usage with Claude Desktop

To use this with Claude Desktop, add the following to your `claude_desktop_config.json`:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json````json
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
``````json
{
  "mcpServers": {
    "datadog": {
      "command": "/path/to/mcp-server-datadog/build/index.js",
      "env": {
        "DATADOG_API_KEY": "<YOUR_API_KEY>",
        "DATADOG_APP_KEY": "<YOUR_APP_KEY>",
        "DATADOG_SITE": "<YOUR_SITE>", // Optional
        "DATADOG_SUBDOMAIN": "<YOUR_SUBDOMAIN>" // Optional
      }
    }
  }
}

Or specify via npx:```json
{
"mcpServers": {
"mcp-server-datadog": {
"command": "npx",
"args": ["-y", "@winor30/mcp-server-datadog"],
"env": {
"DATADOG_API_KEY": "<YOUR_API_KEY>",
"DATADOG_APP_KEY": "<YOUR_APP_KEY>",
"DATADOG_SITE": "<YOUR_SITE>", // Optional
"DATADOG_SUBDOMAIN": "<YOUR_SUBDOMAIN>" // Optional
}
}
}
}


## Debugging

Because MCP servers communicate over standard input/output, debugging can sometimes be tricky. We recommend using the MCP Inspector. You can run the inspector with:```bash
npm run inspector

The inspector will provide a URL you can open in your browser to see logs and send requests manually.

Contributing

Contributions are welcome! Feel free to open an issue or a pull request if you have any suggestions, bug reports, or improvements to propose.

License

This project is licensed under the Apache License, Version 2.0.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Datadog E4bdc072 怎么安装?

在客户端按下面的安装命令接入:npx -y @smithery/cli install @winor30/mcp-server-datadog --client claude。对应的包名是 @smithery/cli。装完在客户端配置里引用同一个包或端点。

MCP Datadog E4bdc072 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Datadog E4bdc072 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Datadog E4bdc072 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

MCP Datadog E4bdc072 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Datadog E4bdc072 能提供哪些能力?

资料显示约 20 个工具;能力标签包括 可观测性、TypeScript、Claude。具体工具清单以官方文档为准。

MCP Datadog E4bdc072 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP Datadog E4bdc072 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。