SigNoz · Cursor
Add the SigNoz MCP server to Cursor
Query metrics, logs and traces, and manage alerts, dashboards, saved views and notification channels in SigNoz.
1. Add the server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"signoz": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/signoz/signoz-mcp-server:v0.15.0"
]
}
}
}Scopes, env vars, OAuth and limits: Cursor MCP config guide
2. Sign in
Cursor prompts you to sign in the first time a remote OAuth server is used. SigNoz runs locally; set any credentials SigNoz asks for before starting Cursor.
3. Try it
Ask Cursor 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.
- · Remote servers take a url; local servers take command and args.
- · Values can reference ${env:NAME} so secrets stay out of the file.
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 Cursor?
- Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.
- 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 Cursor
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 Cursor's documented syntax.