Signoz MCP Server Bda8160c

MCP运维云端

提供方 joshualyon

运维云端 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

Signoz MCP Server是一个暴露Signoz可观测性数据给Claude的服务器,支持通过自然语言查询日志、指标和跟踪数据。

一句话选型结论

按资料字段整理

Signoz MCP Server Bda8160c 属于运维云端类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 3 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量3暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

日志查询TypeScript本地部署指标分析数据发现统一接口生产就绪

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 3 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 3 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Signoz MCP Server Bda8160c当前 3 未标注 未标注 无 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方joshualyon上游标注的维护方 joshualyon
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.1 KB
来自项目仓库与上游目录的原文,未做删改

Signoz MCP Server

An MCP (Model Context Protocol) server that exposes Signoz observability data to Claude, enabling natural language queries against your logs, metrics, and traces.

Features

  • Query Logs: Search and analyze application logs with simple filter syntax
  • Query Metrics: Builder-based metrics querying with aggregation and grouping
  • Discover Data: Explore available metrics and log attributes
  • Unified Interface: Consistent syntax across logs and metrics
  • Type Safety: Robust timestamp handling and parameter validation
  • Production Ready: Comprehensive test coverage and error handling

✅ Implemented

  • ✅ Logs: Querying with pagination and attribute filtering
  • ✅ Metrics: Builder queries with multiple metrics, aggregation, and grouping
  • ✅ Discovery: Metric and log attribute discovery tools
  • ✅ Testing: 45+ tests covering all functionality

🚧 In Development

  • 🚧 Traces: Placeholder - not functional

Prerequisites

  • Signoz 0.85 or later (for API v4 support)
  • Signoz API key
  • One of:
  • Bun runtime (for development)
  • Pre-built binary from Releases

Installation

Option 1: Using Pre-built Binaries (Recommended)

Download the appropriate binary for your platform from the Releases page:
- signoz-mcp-darwin-arm64 - macOS Apple Silicon
- signoz-mcp-darwin-x64 - macOS Intel
- signoz-mcp-linux-x64 - Linux x64
- signoz-mcp-linux-arm64 - Linux arm64
- signoz-mcp-windows-x64.exe - Windows x64

Make it executable (macOS/Linux):```bash
chmod +x signoz-mcp-*


> [!IMPORTANT]
> **macOS Users**: Downloaded binaries are quarantined by Gatekeeper. You have three options:
> 1. Remove quarantine: `xattr -d com.apple.quarantine ./signoz-mcp-darwin-*`
> 2. Run from source using Bun (see Option 2 below)
> 3. Build the binary locally: `bun run build`

### Option 2: Build from Source```bash
# Clone the repository
git clone <repository-url>
cd signoz-mcp-server

# Install dependencies
bun install

Configuration

Claude Code Integration

There are multiple ways to configure the Signoz MCP server with Claude Code:

Method 1: Project Configuration File (Recommended)

Create a .mcp.json file in your project root:```json
{
"mcpServers": {
"signoz": {
"type": "stdio",
"command": "/path/to/signoz-mcp-server-binary",
"env": {
"SIGNOZ_API_KEY": "your-api-key-here",
"SIGNOZ_API_URL": "https://your-signoz-instance.com"
}
}
}
}


Or if running from source:```json
{
  "mcpServers": {
    "signoz": {
      "type": "stdio",
      "command": "bun",
      "args": ["run", "/path/to/signoz-mcp-server/src/server.ts"],
      "env": {
        "SIGNOZ_API_KEY": "your-api-key-here",
        "SIGNOZ_API_URL": "https://your-signoz-instance.com"
      }
    }
  }
}

After creating the file:
1. Exit Claude Code: /exit
2. Restart in the same directory: claude -c
3. Verify the server is loaded: /mcp

> [!TIP]
> Using claude -c will continue your previous Claude Code session, so you won't lose any progress and can continue your existing conversation where you left off.

Method 2: Claude CLI Management```bash

Add server with binary (local to current project)

claude mcp add signoz -s project -e SIGNOZ_API_KEY=your-key -e SIGNOZ_API_URL=https://your-instance.com -- /path/to/signoz-mcp-server-binary

Add server from source

claude mcp add signoz -s project -e SIGNOZ_API_KEY=your-key -e SIGNOZ_API_URL=https://your-instance.com -- bun run /path/to/signoz-mcp-server/src/server.ts

List configured servers

claude mcp list

View server configuration

claude mcp get signoz

Remove server

claude mcp remove signoz


**Scope Options:**
- `--scope local` (default): Available only in current project
- `--scope project`: Shared via `.mcp.json` file
- `--scope user`: Available across all projects

> [!NOTE]
> Local scope configurations are stored in `~/.claude.json` under:
>```json
> {
>   "projects": {
>     "/path/to/project": {
>       "mcpServers": {
>         // your server config here
>       }
>     }
>   }
> }
> ```

#### Method 3: Claude Desktop App

See docs/configuration.md for Claude Desktop configuration details and refer to the example JSON snippets from Method 1 above.

## Usage

### Development```bash
bun run dev

Testing with MCP Inspector```bash

bun run inspector

This will start the MCP Inspector on http://localhost:6274 where you can interactively test the server's tools.

### Build```bash
bun run build

Quick Test```bash

bun run test


## Available Tools

### query_logs
Query application logs from Signoz using simplified filter syntax with clean, readable output.

**Key Features:**
- **Minimal Output by Default**: Clean `[timestamp] [level] [service-context] message` format
- **Smart Service Context**: Shows `[service-name]` or `[namespace/deployment]` automatically
- **Verbose Mode**: Full attribute details when needed (`verbose: true`)
- **Attribute Filtering**: Include only specific attributes (`include_attributes: [...]`)
- **Automatic Pagination**: Handles large result sets with clear instructions for next page

The tool accepts simple filter syntax with these operators:
- `key=value` - Exact match
- `key~value` - Contains (useful for searching in log body)
- `key!=value` - Not equals

Join multiple filters with AND:
- `k8s.deployment.name=stio-api` - Filter by Kubernetes deployment
- `level=error AND service=api-gateway` - Multiple filters
- `body~timeout` - Logs containing "timeout" in the message
- `k8s.namespace=production AND body~error` - Combine resource and content filters

**Output Examples:**

*Default Compact Mode:*```
[2025-06-17T22:26:42Z] [INFO] [default/stio-api]
Set variable $GridPower value as 1.3377999999999999.

[2025-06-17T22:26:41Z] [ERROR] [api-gateway]
Database connection timeout after 30s

[2025-06-17T22:26:40Z] [WARN] [production/user-service]
Rate limit approaching: 450/500 requests

Verbose Mode (verbose: true):```
[2025-06-17T22:26:42Z] [INFO] [default/stio-api]
Set variable $GridPower value as 1.3377999999999999.
Attributes: http.request.id=abc-123 labels.module=rule trace.id=xyz-789

[2025-06-17T22:26:41Z] [ERROR] [api-gateway]
Database connection timeout after 30s
Attributes: error.type=timeout database.name=users http.status=500


*Custom Attributes (include_attributes: ["http.request.id", "trace.id"]):*```
[2025-06-17T22:26:42Z] [INFO] [default/stio-api]
Set variable $GridPower value as 1.3377999999999999.
Attributes: http.request.id=abc-123 trace.id=xyz-789

Query Examples:```
"Show logs from the stio-api deployment"
→ query: "k8s.deployment.name=stio-api"

"Find error logs from the api-gateway service in the last hour"
→ query: "level=error AND service=api-gateway", start: "now-1h"

"Get logs containing 'timeout' from production namespace"
→ query: "k8s.namespace=production AND body~timeout"

"Find logs with database errors, showing trace IDs"
→ query: "body~database AND body~error", include_attributes: ["trace.id"]

"Debug logs with full details"
→ query: "level=debug AND service=user-api", verbose: true


**Pagination Example:**
When results exceed the limit, the tool provides clear instructions:```
--- More Results Available ---
Oldest timestamp: 2025-06-17T23:09:19.025991988Z
To get next 100 older results, use: end="2025-06-17T23:09:19.025991988Z"

query_metrics

Query metrics using a builder-based interface with aggregation and grouping.

Key Features:
- Multiple Metrics: Query multiple metrics in one request
- Aggregation Options: avg, min, max, sum, count
- Grouping: Group results by attributes
- Filter Syntax: Same as logs (key=value, key~contains, key!=value)

Examples:```
"Show CPU utilization for the stio-api deployment"
→ metric: ["k8s_pod_cpu_utilization"], query: "k8s_deployment_name=stio-api"

"Compare CPU and memory usage grouped by pod"
→ metric: ["k8s_pod_cpu_utilization", "k8s_pod_memory_usage"],
group_by: ["k8s_pod_name"], aggregation: "avg"

"Get maximum request rates by status code"
→ metric: ["http_requests_total"], group_by: ["status_code"],
aggregation: "max", query: "service=api-gateway"


### query_traces
Query distributed traces.

Example:```
"Find traces where the total duration exceeded 1 second"

Documentation

  • Usage Examples - Comprehensive examples of log queries and output formats
  • Development Guide - Build, test, and release processes
  • Configuration Guide - Setup and troubleshooting
  • API Integration Guide - Signoz API details and examples
  • Planning Document - Feature roadmap and design decisions

Development

Building```bash

Build for current platform

bun run build

Build for all platforms

bun run build:binary:all

Run tests

bun test
```

Releases

This project uses automated semantic versioning. See Development Guide for details on:
- Commit message conventions
- Automated release process
- Manual release procedures

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feat/amazing-feature)
  3. Commit changes using conventional commits (git commit -m 'feat: add amazing feature')
  4. Push to the branch (git push origin feat/amazing-feature)
  5. Open a Pull Request to main

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Signoz MCP Server Bda8160c 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Signoz MCP Server Bda8160c 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Signoz MCP Server Bda8160c 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Signoz MCP Server Bda8160c 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Signoz MCP Server Bda8160c 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Signoz MCP Server Bda8160c 能提供哪些能力?

资料显示约 3 个工具;能力标签包括 生产就绪、TypeScript、Claude。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。