signoz-mcp-server

Overview

From the repository's own README, as read at the audited commit.

# SigNoz MCP Server[![Go Version](https://img.shields.io/badge/Go-1.26+-blue.svg)](https://golang.org)[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)[![MCP Protocol](https://img.shields.io/badge/MCP-2025--11--25_%7C_2026--07--28-orange.svg)](https://modelcontextprotocol.io)A Model Context Protocol (MCP) server that provides seamless access to SigNoz observability data through AI assistants and LLMs. Query metrics, traces, logs, alerts, dashboards, and services using natural language.**[📖 Full Documentation](https://signoz.io/docs/ai/signoz-mcp-server/)**## Table of Contents- [Connect to SigNoz Cloud](#connect-to-signoz-cloud)- [Self-Hosted Installation](#self-hosted-installation)- [Connect to Self-Hosted SigNoz](#connect-to-self-hosted-signoz)- [MCP Protocol Compatibility](#mcp-protocol-compatibility)- [What Can You Do With It?](#what-can-you-do-with-it)- [Available Tools](#available-tools)- [Environment Variables](#environment-variables)- [Claude Desktop Extension](#claude-desktop-extension)- [End-to-End Tests](#end-to-end-tests)- [Architecture](#architecture)- [Contributing](#contributing)## Connect to SigNoz CloudConnect your AI tool to SigNoz Cloud's hosted MCP server. No installation is required; just add the hosted MCP URL and authenticate.```texthttps://mcp.<region>.signoz.cloud/mcp```> Make sure you select the correct region that matches your SigNoz Cloud account. Using the wrong region will result in authentication failures.>> Find your region under **Settings → Ingestion** in SigNoz, or see the [SigNoz Cloud region reference](https://signoz.io/docs/ingestion/signoz-cloud/overview/#endpoint).### One-Click Install LinksGitHub does not reliably make custom-protocol links like `cursor://` and `vscode:` clickable in README rendering.Use the documentation page for one-click install buttons:- [Open one-click install links for Cursor](https://signoz.io/docs/ai/signoz-mcp-server/#install-in-one-click)- [Open one-click install links

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude mcp add signoz-mcp-server:v0.14.0 -- docker run -i --rm docker.io/signoz/signoz-mcp-server:v0.14.0:None

Details

Source

SigNoz/signoz-mcp-server

npm

signoz-mcp-protocol-ci@1.0.0

PyPI

signoz-mcp-server-tests

Transports

stdio · streamable-http

Credentials it reads

GITHUB_TOKEN

Tools

Registered at runtime; the list could not be read from source.

License

Apache-2.0

Stars

119 · pushed 0d ago

Trust audit

Install with care. The audit found things worth knowing before you trust its output.

What the source does

Filesystem

none-observed

Network

declared (3 observation(s))

Shell

none-observed

Dependencies

pinned

Secrets in source

found

Findings (23)

"sk_live_suggestioncanary123456",

"sk_live_detailcanary123456",

"sk_live_detailhintcanary123456",

.goreleaser.yaml

AGENTS.md

"169.254.169.254", // SSRF target blocked once an allowlist is set

server --url http://127.0.0.1:<port>/mcp \

return &localHTTPTestServer{URL: "http://127.0.0.1", handler: handler}

url:  "https://1.1.1.1:443",

want: "https://1.1.1.1",

url:  "http://1.1.1.1:80",

When OAuth is enabled, the middleware first tries to decrypt an `Authorization` Bearer token as a server-issued OAuth access token; a valid one unwraps to a stored API key forwarded via `SIGNOZ-API-KE

assigning viewer access or creating/revoking credentials.

read-only, avoid logging credentials, and report whether a real recognized

- Do not retry or route around the policy. Ask the user for explicit approval after disclosing the risk. If approved, keep the routing suite non-executing and run only a separately identified read-onl

7. Attempt a separate delegated read-only staging smoke subset with credentials supplied only through process environment. Do not execute mutations. If organization policy prohibits sending private st

Verifying against a live SigNoz instance (creating/reading/updating/deleting real alerts, dashboards, or views, or any multi-step API probing with credentials) should be delegated to a subagent (Agent

Since tokens are self-contained encrypted blobs, any server instance with the same `OAUTH_TOKEN_SECRET` can validate any token. No sticky sessions or shared state needed. The only requirement is that 

The Streamable HTTP transport runs stateless (`WithStateLess(true)`; see [architecture.md](architecture.md)) — no `Mcp-Session-Id` is issued and there is no server-owned session lifecycle to report. T

This is materially different from the post-decrypt OAuth paths (`handleAuthorizationCodeGrant`, `handleRefreshTokenGrant`, `issueTokenPair`), where `signozURL` comes out of an encrypted token the **se

- `README.md`: supported protocol-era/transport table, `server/discover` and legacy initialize behavior, stateless POST-only endpoint, no session ID, and unchanged client configuration.

internal/docs/assets/corpus.gob.gz

Gates applied: no_behavioural_pass.

Audited 2026-09-15 · audit v0.4.0 · source sha 6929851bea7b · full audit: observations/trust-audit/mcp-server/signoz__signoz-mcp-server.json · Report an issue or request a re-scan

Audit history

Alternatives

Other servers in the same categories, safer ones first.

Questions