SigNoz MCP server

What the model can do

SigNoz observability (Cloud or self-hosted): alert rules and their state, alerts firing now, a rule's state history, dashboards, metric names, planned maintenance windows, and aggregate queries over logs, traces and metrics (counts, rates, percentiles grouped by service or other fields); when you ask, can enable or disable, clone or delete an alert rule, create, change or delete a maintenance window that mutes alerts, and clone, lock, unlock or delete a dashboard.

Reads

• signoz_alert_rulesSigNoz alert rules: name, type (metrics, logs, traces, exceptions), state (firing, pending, recovering, inactive, nodata, disabled)…
• signoz_alert_ruleOne SigNoz alert rule in full: state, evaluation window and frequency, thresholds, annotations and the channels it notifies.
• signoz_firing_alertsAlerts SigNoz's alert manager holds right now (firing, or silenced and inhibited ones): the alert name, severity, labels, summary…
• signoz_rule_historyWhen a SigNoz alert rule changed state (fired, resolved, went to nodata) in a window: each transition with its time, state, value and labels.
• signoz_dashboardsSigNoz dashboards: name, tags, whether locked, who created and last changed them.
• signoz_queryAggregate query over SigNoz logs, traces or metrics for a time window: a count, rate, average or percentile…
• signoz_metricsMetric names SigNoz has received, with type, unit, temporality and description, matched by a substring.
• signoz_maintenance_windowsSigNoz planned maintenance (downtime) windows that mute alert rules: name, status (active, upcoming, expired), schedule…

Acts, when you ask

These change something in SigNoz. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• signoz_set_alert_rule_enabledEnables or disables a SigNoz alert rule.
• signoz_clone_alert_ruleCopies a SigNoz alert rule into a new rule named "<name> - Copy", owned by the service account.
• signoz_delete_alert_rulePermanently deletes a SigNoz alert rule; whatever it monitored stops paging anyone.
• signoz_create_maintenance_windowCreates a SigNoz planned maintenance window that mutes the named alert rules for a time span (once, or repeating daily, weekly or monthly)…
• signoz_update_maintenance_windowReplaces a SigNoz planned maintenance window's name, rules and schedule with what you give (SigNoz replaces the whole window…
• signoz_delete_maintenance_windowPermanently deletes a SigNoz planned maintenance window; the rules it muted page their channels again straight away if they are firing.
• signoz_clone_dashboardCopies a SigNoz dashboard (panels and tags) into a new unlocked dashboard owned by the service account; system dashboards cannot be cloned.
• signoz_set_dashboard_lockLocks a SigNoz dashboard so nobody can edit or delete it, or unlocks it.
• signoz_delete_dashboardPermanently deletes a SigNoz dashboard and its panels for everyone; a locked dashboard is refused.

Connect it

First connect SigNoz on Dashboard → Connections, then add Memtro to your client once. The SigNoz tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared SigNoz connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which SigNoz alerts are firing right now?
• › How many errors did checkout log in the last hour?
• › What is the p99 latency of the payments service today?
• › When did the High CPU rule last fire and resolve?
• › Which maintenance windows are coming up this week?

Questions

Is this an official SigNoz MCP server?

No. It is Memtro's MCP server with Memtro's SigNoz connector behind it: the connector reads SigNoz through its API with the credentials you connect on Dashboard → Connections, and SigNoz publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in SigNoz?

Only when you ask, and only what it has been granted: enable or disable an alert rule; clone an alert rule; delete an alert rule; create a planned maintenance window that mutes named alert rules; change a planned maintenance window; delete a planned maintenance window; clone a dashboard; lock or unlock a dashboard; delete a dashboard. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server