SigNoz MCP Server

Query SigNoz logs, traces, metrics, dashboards and alerts.

By defaultCan write
Safest setupNo read-only mode Use a read-only credential

Labels are provisional (from the project README/docs, checked Oct 27, 2026). Not yet tested in our sandbox.

Read-only switch

No read-only switch found in the README.

Preset

No read-only switch. This config is the vendor default plus an approval prompt on every tool. It is not read-only. The credential is what protects you.

Claude Code

.mcp.json
{
  "mcpServers": {
    "signoz": {
      "type": "http",
      "url": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}
.claude/settings.json
{
  "permissions": {
    "ask": ["mcp__signoz"]
  }
}

ask makes Claude Code prompt before every tool from this server.

Codex

~/.codex/config.toml
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.

[mcp_servers.signoz]
url = "https://mcp.<region>.signoz.cloud/mcp"
default_tools_approval_mode = "prompt"

default_tools_approval_mode = "prompt" asks before every tool call.

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "signoz": {
      "url": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.

Credential layer

Use a SigNoz API key from a Viewer-role user.

Facts

Vendor
SigNoz official
Source
SigNoz/signoz-mcp-server
License
Apache-2.0
GitHub stars
128
Latest release
v0.16.0 (Oct 23, 2026)
Last push
Oct 27, 2026
Status
Active
Last checked
Oct 27, 2026

Sources

  • README · checked Oct 27, 2026

Spotted something wrong? Labels change when vendors change. Suggest a correction

Read-only alternatives in Observability