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.
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.15.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.
Get the weekly agent stack update
New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.
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
Work at SigNoz?
Feature SigNoz across the directory and its category from $49/month.
Reviewed Oct 20, 2026. Command generated from the registry record and checked against Codex's documented syntax.