REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"metricwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/metricwatch",
"mcp"
]
}
}
}Use Metricwatch and tell me what you can do for me, then show me one thing✓ If Claude says it is using Metricwatch or shows a Metricwatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Metricwatch yet
Metricwatch runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Metricwatch
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user metricwatch -- npx -y @reneturcios/metricwatch mcpYou should see Metricwatch listed as connected
Use Metricwatch and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Metricwatch or shows a Metricwatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Metricwatch and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Metricwatch or shows a Metricwatch tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Metricwatch and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Metricwatch or shows a Metricwatch tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user metricwatch -- npx -y @reneturcios/metricwatch mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"metricwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/metricwatch",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"metricwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/metricwatch",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"metricwatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/metricwatch",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
Code last changed 11 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 11 days ago, and the latest version (0.1.0) reached the registry 11 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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. . When either key is missing, every call fails with an error that names the missing variable.
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.
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=
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.
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" } } } }
| 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.
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
MIT — see LICENSE.