Main
Start with self-hosted stdio mode if you already run SigNoz: add the binary to your MCP client config and pass
SIGNOZ_URL+SIGNOZ_API_KEYas env.Use Docker HTTP mode when you want a fixed port and simpler deployment; README provides a
docker runexample withTRANSPORT_MODE=http.Version-pin SigNoz APIs: README notes SigNoz v0.120.0+ is required for some alert rule tools (v2 rules APIs).
Source-backed notes
- README says only Admin users can create API keys in SigNoz (Settings → API Keys).
- README includes
go install ...@latestand a rename step to get asignoz-mcp-serverbinary on PATH. - README documents stdio MCP config with
SIGNOZ_URLandSIGNOZ_API_KEYenv vars, plus Docker HTTP mode examples.
FAQ
- Do I need SigNoz Cloud?: No — README describes connecting to self-hosted instances via URL + API key.
- What’s the safest first run?: Use read-only query tools first and confirm API key scope before automations that mutate alerts.
- How do I deploy it without Go?: README offers release binaries and Docker images in addition to
go install.