Metricwatch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 1, 2026

Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.

VerifiedSTDIODesktop onlySecurity & Monitoring Data & Analytics

Server details

Identifier: io.github.CloudCorpRecords/metricwatch
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 1, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account CloudCorpRecords for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CloudCorpRecords%2Fmetricwatch.svg)](https://sourceweft.com/mcp/io.github.CloudCorpRecords%2Fmetricwatch?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Read-only MCP server that lets an assistant query Datadog metrics, dashboards, logs, incidents, monitors and downtimes from your account.

What you can do: Query metric timeseries over a time range and list metric names with their type, unit and description
List dashboards and fetch one dashboard with its widgets and layout
Search log events with a log query over an optional time range
List incidents and fetch a single incident by id
List monitors, optionally filtered by name, and fetch one monitor by integer id
List downtimes (scheduled monitor silences)
When to use it: Useful when you want an assistant to investigate Datadog telemetry during debugging or incident review: checking a metric's trend, reading a dashboard, searching error logs, or looking up a monitor or incident. It is read-only, so it suits exploration and reporting rather than changing Datadog configuration.
Requirements: Runs locally over stdio via npx or the Docker image. Needs a Datadog API key in DATADOG_API_KEY and an application key in DATADOG_APP_KEY, sent as the DD-API-KEY and DD-APPLICATION-KEY headers. Optionally set DATADOG_SITE to target another Datadog site; the default is datadoghq.com. Network access to the Datadog API is required.

Before you install

Requires two Datadog credentials, DATADOG_API_KEY and DATADOG_APP_KEY, which grant read access to your account's metrics, logs, dashboards, incidents and monitors; keep them in the client's environment configuration. Queries and log searches are sent to the Datadog API at the configured site. The README states the keys never appear in output, but review before sharing results.

Installation

In SourceWeft

Open Metricwatch in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

metricwatch

metricwatch gives an MCP client or a terminal read access to a Datadog account: metric timeseries queries and metric metadata, dashboards, log search, incidents, monitors, and downtimes. It is a clean-room rebuild of the Datadog MCP tool surface from Datadog's public API documentation, covering the read core listed below.

Two credentials are required, because the Datadog API requires both on every call: an API key in DATADOG_API_KEY and an application key in DATADOG_APP_KEY. They are sent as the DD-API-KEY and DD-APPLICATION-KEY headers and never appear in output. Set DATADOG_SITE (for example datadoghq.eu) to target a different Datadog site; the default is datadoghq.com and calls go to https://api.<site>. When either key is missing, every call fails with an error that names the missing variable.

Install

Or run the container image:

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

Every MCP tool is also a CLI subcommand. Tool arguments are passed as one JSON object with --json:

bash

export DATADOG_API_KEY=<redacted>export DATADOG_APP_KEY=<redacted>
metricwatch query_timeseries --json '{"from": 1700000000, "to": 1700003600, "query": "avg:system.cpu.user{*}"}'metricwatch list_metrics --json '{"limit": 20}'metricwatch get_dashboard --json '{"dashboard_id": "abc-123"}'metricwatch search_logs --json '{"query": "service:web status:error", "limit": 25}'metricwatch list_monitorsmetricwatch get_monitor --json '{"monitor_id": 42}'
metricwatch --version

export DATADOG_API_KEY=<redacted>export DATADOG_APP_KEY=<redacted>
metricwatch query_timeseries --json '{"from": 1700000000, "to": 1700003600, "query": "avg:system.cpu.user{*}"}'metricwatch list_metrics --json '{"limit": 20}'metricwatch get_dashboard --json '{"dashboard_id": "abc-123"}'metricwatch search_logs --json '{"query": "service:web status:error", "limit": 25}'metricwatch list_monitorsmetricwatch get_monitor --json '{"monitor_id": 42}'
metricwatch --version

Results print as JSON. Exit codes: 0 on success, 1 when an API call fails (including a missing key), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

MCP client configuration:

json

{  "mcpServers": {    "metricwatch": {      "command": "npx",      "args": ["-y", "@reneturcios/metricwatch", "mcp"],      "env": {        "DATADOG_API_KEY": "your Datadog API key",        "DATADOG_APP_KEY": "your Datadog application key"      }    }  }}

{  "mcpServers": {    "metricwatch": {      "command": "npx",      "args": ["-y", "@reneturcios/metricwatch", "mcp"],      "env": {        "DATADOG_API_KEY": "your Datadog API key",        "DATADOG_APP_KEY": "your Datadog application key"      }    }  }}

Tools

Tool	Input (required in bold)	What it does
`query_timeseries`	`from`, `to`, `query`	Queries a metric timeseries (v1 query endpoint).
`list_metrics`	`from`, `limit`	Lists metric names in the account.
`get_metric_metadata`	`metric_name`	Returns one metric's type, unit, and description.
`list_dashboards`	`limit`	Lists dashboards.
`get_dashboard`	`dashboard_id`	Returns one dashboard with its widgets.
`search_logs`	`query`, `from`, `to`, `limit`	Searches log events (v2 logs search).
`list_incidents`	`limit`	Lists incidents.
`get_incident`	`incident_id`	Returns one incident.
`list_monitors`	`name`, `limit`	Lists monitors, optionally name-filtered.
`get_monitor`	`monitor_id`	Returns one monitor by integer id.
`list_downtimes`	`current_only`	Lists downtimes (monitor silences).

Out of scope for this read core: APM trace/span detail, synthetics, RUM, notebooks, SLO administration, event writes, incident creation or mutation, and on-call — see BUILD-REPORT.md.

Development

bash

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit fbed34a

Tools

query_timeseries

Query a Datadog metric timeseries over a time range using the metrics query language.

Parameterstorequiredfromrequiredqueryrequired

list_metrics

List metric names available in the Datadog account.

Parametersfromlimit

get_metric_metadata

Get metadata for one metric: its type, unit, and description.

Parametersmetric_namerequired

list_dashboards

List dashboards in the Datadog account.

Parameterslimit

get_dashboard

Get one dashboard by id, including its widgets and layout.

Parametersdashboard_idrequired

search_logs

Search Datadog log events with a log query over an optional time range.

Parameterstofromlimitqueryrequired

list_incidents

List Datadog incidents.

Parameterslimit

get_incident

Get one incident by id.

Parametersincident_idrequired

list_monitors

List monitors, optionally filtered by name.

Parametersnamelimit

get_monitor

Get one monitor by its integer id.

Parametersmonitor_idrequired

list_downtimes

List downtimes (scheduled monitor silences).

Parameterscurrent_only

Version history

v0.1.0LatestNov 1, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts