Skip to content
AgentAtlas

SigNoz · Codex

Add the SigNoz MCP server to Codex

Query metrics, logs and traces, and manage alerts, dashboards, saved views and notification channels in SigNoz.

Official serverLocalObservability & incidents

1. Add the server

Run in your terminal

# ~/.codex/config.toml
[mcp_servers.signoz]
command = "docker"
args = ["run", "-i", "--rm", "docker.io/signoz/signoz-mcp-server:v0.18.0"]

Scopes, env vars, OAuth and limits: Codex MCP config guide

2. Sign in

Run codex mcp login <name> to complete OAuth for a remote server. SigNoz runs locally; set any credentials SigNoz asks for before starting Codex.

3. Try it

Ask Codex for something SigNoz can do. Query metrics, logs and traces, and manage alerts, dashboards, saved views and notification channels in SigNoz. Approve the first tool call and check the result before allowing write actions automatically.

  • · Each server is a [mcp_servers.<name>] table in config.toml.
  • · Use enabled_tools or disabled_tools to keep the tool list short.

FAQ

How do I add the SigNoz MCP server to Codex?
Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
Is this the official SigNoz MCP server?
Yes. It is published by SigNoz as io.github.SigNoz/signoz-mcp-server in the official MCP registry.
Does the SigNoz MCP server need an API key?
It runs locally from a package. See SigNoz's docs for any credentials it needs.

Links

SigNoz in other clients

More observability & incidents for Codex

Built an MCP server? Get it listed everywhere →

Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →

Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.