# SigNoz MCP Server — Query Traces, Logs & Alerts

> SigNoz MCP Server connects MCP clients to your SigNoz instance: query traces/logs, inspect alerts, and automate observability workflows using an API key.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
go install github.com/SigNoz/signoz-mcp-server/cmd/server@latest
mv "$(go env GOPATH)/bin/server" "$(go env GOPATH)/bin/signoz-mcp-server"
# Set env vars in your MCP config:
# SIGNOZ_URL=... SIGNOZ_API_KEY=... LOG_LEVEL=info
```

## Intro

SigNoz MCP Server connects MCP clients to your SigNoz instance: query traces/logs, inspect alerts, and automate observability workflows using an API key.

**Best for:** On-call engineers who want agents to triage incidents from traces and logs

**Works with:** SigNoz instance + API key, stdio MCP clients, Go binary or Docker

**Setup time:** 6-18 minutes

### Key facts (verified)

- GitHub: 92 stars · 31 forks · pushed 2026-05-13.
- License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
- README-verified entrypoint: `go install github.com/SigNoz/signoz-mcp-server/cmd/server@latest`.

## 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_KEY` as env.

- Use Docker HTTP mode when you want a fixed port and simpler deployment; README provides a `docker run` example with `TRANSPORT_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 ...@latest` and a rename step to get a `signoz-mcp-server` binary on PATH.
- README documents stdio MCP config with `SIGNOZ_URL` and `SIGNOZ_API_KEY` env 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`.

## Source & Thanks

> Source: https://github.com/SigNoz/signoz-mcp-server
> License: Apache-2.0
> GitHub stars: 92 · forks: 31

---

<!-- ZH -->

## Quick Use

```bash
go install github.com/SigNoz/signoz-mcp-server/cmd/server@latest
mv "$(go env GOPATH)/bin/server" "$(go env GOPATH)/bin/signoz-mcp-server"
# Set env vars in your MCP config:
# SIGNOZ_URL=... SIGNOZ_API_KEY=... LOG_LEVEL=info
```

## Intro

SigNoz MCP Server 让 MCP 客户端直连你的 SigNoz：通过 API key 查询 trace/log、检查告警与规则，适合把可观测性排障流程交给 agent 自动化执行。

**Best for:** 想让 agent 参与 on-call 排障、从 trace/log 定位问题的工程师

**Works with:** SigNoz 实例 + API key；stdio MCP 客户端；Go 二进制或 Docker

**Setup time:** 6-18 minutes

### Key facts (verified)

- GitHub：92 stars · 31 forks；最近更新 2026-05-13。
- 许可证：Apache-2.0；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中核对过的入口命令：`go install github.com/SigNoz/signoz-mcp-server/cmd/server@latest`。

## Main

- 已有 SigNoz 的话优先走 stdio：把二进制挂到 MCP 客户端配置里，并通过 env 传 `SIGNOZ_URL` 与 `SIGNOZ_API_KEY`。

- 想要固定端口/更易部署可用 Docker HTTP：README 给出 `TRANSPORT_MODE=http` 的 `docker run` 示例。

- 注意版本要求：README 提到某些告警规则工具需要 SigNoz v0.120.0+（v2 rules API）。

### Source-backed notes

- README 提到：SigNoz 的 API key 需要在 Settings → API Keys 创建，且仅 Admin 可创建。
- README 提供 `go install ...@latest`，并给出重命名步骤把二进制变成 `signoz-mcp-server`。
- README 给出 stdio MCP 配置（env 传 `SIGNOZ_URL`/`SIGNOZ_API_KEY`），也提供 Docker HTTP 模式示例。

### FAQ

- **必须用 SigNoz Cloud 吗？**：不必。README 支持用 URL + API key 连接自托管实例。
- **最安全的起步方式？**：先跑只读查询工具，确认 API key 权限范围，再考虑自动化改告警规则等操作。
- **不装 Go 能部署吗？**：可以。README 提供 releases 二进制与 Docker 镜像两条路。

## Source & Thanks

> Source: https://github.com/SigNoz/signoz-mcp-server
> License: Apache-2.0
> GitHub stars: 92 · forks: 31


---
Source: https://tokrepo.com/en/workflows/signoz-mcp-server-query-traces-logs-alerts
Author: MCP Hub