English Français العربية

io.github.CloudCorpRecords/metricwatch

Official registry Other

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @reneturcios/metricwatch
Claude Code 
claude mcp add metricwatch -- npx -y @reneturcios/metricwatch@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "metricwatch": {
            "command": "npx",
            "args": [
                "-y",
                "@reneturcios/metricwatch@0.1.0",
                "mcp"
            ]
        }
    }
}
OCI package ghcr.io/cloudcorprecords/metricwatch:0.1.0
Claude Code 
claude mcp add metricwatch -- docker run -i --rm ghcr.io/cloudcorprecords/metricwatch:0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "metricwatch": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cloudcorprecords/metricwatch:0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. metricwatch
  2. Install
  3. CLI
  4. MCP server
  5. Development
  6. License

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

npx @reneturcios/metricwatch list_metrics

Or run the container image:

docker run -i -e DATADOG_API_KEY -e DATADOG_APP_KEY ghcr.io/cloudcorprecords/metricwatch

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:

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_monitors
metricwatch 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:

npx -y @reneturcios/metricwatch mcp

MCP client configuration:

{
  "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
ToolInput (required in bold)What it does
query_timeseriesfrom, to, queryQueries a metric timeseries (v1 query endpoint).
list_metricsfrom, limitLists metric names in the account.
get_metric_metadatametric_nameReturns one metric's type, unit, and description.
list_dashboardslimitLists dashboards.
get_dashboarddashboard_idReturns one dashboard with its widgets.
search_logsquery, from, to, limitSearches log events (v2 logs search).
list_incidentslimitLists incidents.
get_incidentincident_idReturns one incident.
list_monitorsname, limitLists monitors, optionally name-filtered.
get_monitormonitor_idReturns one monitor by integer id.
list_downtimescurrent_onlyLists 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

npm install
npm 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.

Frequently asked questions

What is io.github.CloudCorpRecords/metricwatch?

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

How do I install io.github.CloudCorpRecords/metricwatch?

It runs on your machine. In Claude Code: claude mcp add metricwatch -- npx -y @reneturcios/metricwatch@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.CloudCorpRecords/metricwatch need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.CloudCorpRecords/metricwatch open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.CloudCorpRecords/metricwatch?

It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.