Show HN: Metrics, Monitoring, and Alerting for Agents

MCP server for the ChirrOp monitoring platform. Exposes the full ChirrOp API as tools, resources, and prompts for any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.).

npm install @chirropjs/chirrop-mcp

Or run directly:

npx @chirropjs/chirrop-mcp

These are two separate kinds of variable on purpose. CHIRROP_API_KEY is the server's own credential and can never be referenced from a tool call. Only CHIRROP_SECRET_-prefixed variables can, so a prompt-injected request can't send your API key to an attacker's webhook.

Set the variables wherever your MCP client launches the server. The server does not read .env files itself.

Pass the key when adding the server:

claude mcp add chirrop -e CHIRROP_API_KEY=chp_your_api_key -- npx -y @chirropjs/chirrop-mcp

To keep the key out of a committed .mcp.json, export it in your shell instead and reference it from the config:

export CHIRROP_API_KEY=chp_your_api_key
{
  "mcpServers": {
    "chirrop": {
      "command": "npx",
      "args": ["-y", "@chirropjs/chirrop-mcp"],
      "env": {
        "CHIRROP_API_KEY": "${CHIRROP_API_KEY}"
      }
    }
  }
}

Claude Code expands ${CHIRROP_API_KEY} from the environment it was started in, so export the variable before running claude, then check the connection with /mcp.

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "chirrop": {
      "command": "npx",
      "args": ["-y", "@chirropjs/chirrop-mcp"],
      "env": {
        "CHIRROP_API_KEY": "chp_your_api_key"
      }
    }
  }
}

Slack, Discord and webhook URLs and Telegram bot tokens are secrets. Rather than pasting them into the conversation, add them to the server's environment with a CHIRROP_SECRET_ prefix:

"env": {
  "CHIRROP_API_KEY": "chp_your_api_key",
  "CHIRROP_SECRET_SLACK_URL": "https://hooks.slack.com/services/T000/B000/XXXX",
  "CHIRROP_SECRET_TELEGRAM_TOKEN": "123456:ABC-your-bot-token"
}

Then refer to them by name when creating or updating a destination, e.g. "create a Slack destination using env:CHIRROP_SECRET_SLACK_URL". The tool call then contains:

{ "channel": "slack", "url": "env:CHIRROP_SECRET_SLACK_URL", "scope": "all", "policy_ids": [], "enabled": true }

• References to any variable without the CHIRROP_SECRET_ prefix (includingCHIRROP_API_KEY ) are refused.

• Restart the server after adding a variable; a reference to an unset variable returns an error.

• Destination URLs and credentials are redacted in everything the server returns (tools and thechirrop://destinations resource), e.g.https://hooks.slack.com/[redacted] . Emailaddress and Telegramchat_id stay visible because they identify the recipient rather than authenticate.

• Event references : every tool that takes anevent_id (UUID) also acceptsevent (the event name) plus an optionalagent — the server resolves the UUID for you.compare_events accepts a mix of UUIDs and exact names.

• Pagination :list_events andlist_alerts default to 50 results and returnhas_more /next_offset for paging.

• Cheap reads :get_event_rollups supportssummary_only=true to return just the statistical summary plus anomalous buckets.

• Timestamps : time-series and health responses includeretrieved_at so staleness can be reasoned about reliably.

• Secrets : destinationurl andcredentials values acceptenv:CHIRROP_SECRET_<NAME> references and are redacted in output. SeeDestination secrets .

• Idempotent logging :send_logs returns thelog_id of every entry (generated if you didn't supply one). If a send fails, retry with the samelog_id s so nothing is double-counted.

• Health checks :get_stream_health andget_agent_summary compare each policy's threshold against the latest bucket of that policy's own period (minute/hour/day). Inget_agent_summary , a stream whose data couldn't be fetched showsstatus: "error" with the reason, rather than appearing stale.

• No deletes : the ChirrOp API has no delete operations. Retire policies and destinations by settingenabled: false ; event definitions cannot be removed.

git clone https://github.com/chirrop/chirrop-mcp
cd chirrop-mcp
npm install
npm run build

Run the tests:

npm test

Test with the MCP Inspector:

CHIRROP_API_KEY=chp_your_key npx @modelcontextprotocol/inspector node dist/index.js

MIT