Signoz MCP Server Fc3aa65b

MCP运维云端

提供方 BachNgoH

运维云端 未标注 Token 社区 / 第三方 Claude DesktopClaudeCursor

SigNoz MCP Server是一款通过AI助手和LLM提供自然语言查询的可观测性数据访问服务器,支持指标、追踪、日志、告警等多种数据的查询与分析。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

支持客户端

适用场景

可观测性Go本地部署自然语言查询AI助手集成日志分析指标监控

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

部署与发布

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

监控与告警

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

选择建议

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

值得选的地方

  • 资料标注 19 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Signoz MCP Server Fc3aa65b当前 19 未标注 未标注 无 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

服务器档案

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

详细介绍

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

SigNoz MCP Server

A Model Context Protocol (MCP) server that provides seamless access to SigNoz observability data through AI assistants and LLMs. This server enables natural language queries for metrics, traces, logs, alerts, dashboards, and service performance data.

🚀 Features

  • List Metric Keys: Retrieve all available metric keys from SigNoz.
  • Search Metric Keys: Find specific metrics.
  • List Alerts: Get all active alerts with detailed status.
  • Get Alert Details: Retrieve comprehensive information about specific alert rules.
  • Get Alert History: Gives you timeline of an alert.
  • Logs: Gets log related to services, alerts, etc.
  • Traces: Search, analyze, get hierarchy and relationship of traces.
  • List Dashboards: Get dashboard summaries (name, UUID, description, tags).
  • Get Dashboard: Retrieve complete dashboard configurations with panels and queries.
  • List Services: Discover all services within specified time ranges.
  • Service Top Operations: Analyze performance metrics for specific services.
  • Query Builder: Generates query to get complex response.

🏗️ Architecture```

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ MCP Client │───▶│ MCP Server │───▶│ SigNoz API │
│ (AI Assistant) │ │ (Go) │ │ (Observability)│
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌──────────────────┐
│ Tool Handlers │
│ (HTTP Client) │
└──────────────────┘


### Core Components

- **MCP Server**: Handles MCP protocol communication
- **Tool Handlers**: Register and manage available tools
- **SigNoz Client**: HTTP client for SigNoz API interactions
- **Configuration**: Environment-based configuration management
- **Logging**: Structured logging with Zap

## 🧰 Usage

Use this mcp-server with MCP-compatible clients like Claude Desktop and Cursor.

### Claude Desktop

1. Build or locate the binary path for `signoz-mcp-server` (for example: `.../signoz-mcp-server/bin/signoz-mcp-server`).
2. Goto Claude -> Settings -> Developer -> Local MCP Server click on `edit config`
3. Edit `claude_desktop_config.json` Add shown config with your signoz url, api key and path to signoz-mcp-server binary.```json
{
  "mcpServers": {
    "signoz": {
      "command": "/absolute/path/to/signoz-mcp-server/bin/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "https://your-signoz-instance.com",
        "SIGNOZ_API_KEY": "your-api-key-here",
        "LOG_LEVEL": "info"
      }
    }
  }
}
  1. Restart Claude Desktop. You should see the signoz server load in the developer console and its tools become available.

Notes:
- Replace the command path with your actual binary location.

Cursor

Option A — GUI:
- Open Cursor → Settings → Cursor Settings → Tool & Integrations → + New MCP Server

Option B — Project config file:
Create .cursor/mcp.json in your project root:

For Both options use same json struct```json
{
"mcpServers": {
"signoz": {
"command": "/absolute/path/to/signoz-mcp-server/bin/signoz-mcp-server",
"args": [],
"env": {
"SIGNOZ_URL": "https://your-signoz-instance.com",
"SIGNOZ_API_KEY": "your-api-key-here",
"LOG_LEVEL": "info"
}
}
}
}


Once added, restart Cursor to use the SigNoz tools.

### HTTP based self hosted mcp server

### Claude Desktop

1. Build and run signoz-mcp-server with envs
   - SIGNOZ_URL=signoz_url SIGNOZ_API_KEY=signoz_apikey TRANSPORT_MODE=http MCP_SERVER_PORT=8000 LOG_LEVEL=log_level ./signoz-mcp-server
   - or use docker-compose
2. Goto Claude -> Settings -> Developer -> Local MCP Server click on `edit config`
3. Edit `claude_desktop_config.json` Add shown config with your signoz url, api key and path to signoz-mcp-server binary.```json
{
  "mcpServers": {
    "signoz": {
      "url": "http://localhost:8000/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key-here"
      }
    }
  }
}

Note: You can pass the SigNoz API key either as:
- An environment variable (SIGNOZ_API_KEY) when starting the server, or
- Via the Authorization header in the client configuration as shown above

  1. Restart Claude Desktop. You should see the signoz server load in the developer console and its tools become available.

Cursor

Build and run signoz-mcp-server with envs
- SIGNOZ_URL=signoz_url SIGNOZ_API_KEY=signoz_apikey TRANSPORT_MODE=http MCP_SERVER_PORT=8000 LOG_LEVEL=log_level ./signoz-mcp-server
- or use docker-compose

Option A — GUI:
- Open Cursor → Settings → Cursor Settings → Tool & Integrations → + New MCP Server

Option B — Project config file:
Create .cursor/mcp.json in your project root:

For Both options use same json struct```json
{
"mcpServers": {
"signoz": {
"url": "http://localhost:8000/mcp",
"headers": {
"Authorization": "Bearer signoz-api-key-here"
}
}
}
}


**Note:** You can pass the SigNoz API key either as:
- An environment variable (`SIGNOZ_API_KEY`) when starting the server, or
- Via the `Authorization` header in the client configuration as shown above

**Note:** By default, the server logs at `info` level. If you need detailed debugging information, set `LOG_LEVEL=debug` in your environment. For production use, consider using `LOG_LEVEL=warn` to reduce log verbosity.

## 🛠️ Development Guide

### Prerequisites

- Go 1.25 or higher
- SigNoz instance with API access
- Valid SigNoz API key

### Project Structure```
signoz-mcp-server/
├── cmd/server/           # Main application entry point
├── internal/
│   ├── client/          # SigNoz API client
│   ├── config/          # Configuration management
│   ├── handler/tools/   # MCP tool implementations
│   ├── logger/          # Logging utilities
│   └── mcp-server/      # MCP server core
├── go.mod               # Go module dependencies
├── Makefile             # Build automation
└── README.md

Building from Source```bash

Clone the repository

git clone https://github.com/SigNoz/signoz-mcp-server.git
cd signoz-mcp-server

Build the binary

make build

Or build directly with Go

go build -o bin/signoz-mcp-server ./cmd/server/


### Configuration

Set the following environment variables:```bash

export SIGNOZ_URL="https://your-signoz-instance.com"
export SIGNOZ_API_KEY="your-api-key-here"
export LOG_LEVEL="info"  # Optional: debug, info, error (default: info)

In SigNoz Cloud, SIGNOZ_URL is typically - https://ingest..signoz.cloud

You can access API Key by going to Settings -> Workspace Settings -> API Key in SigNoz UI

Running the Server```bash

Run the built binary

./bin/signoz-mcp-server


### Development Workflow

1. **Add New Tools**: Implement in `internal/handler/tools/`
2. **Extend Client**: Add methods to `internal/client/client.go`
3. **Register Tools**: Add to appropriate handler registration
4. **Test**: Use MCP client to verify functionality

## 📖 User Guide

### For AI Assistants & LLMs

The MCP server provides the following tools that can be used through natural language:

#### Metrics Exploration```
"Show me all available metrics"
"Search for CPU-related metrics"

Alert Monitoring```

"List all active alerts"
"Get details for alert rule ID abc123"
"Show me the history for alert rule abc123 from the last 24 hours"
"Get logs related to alert abc456"


#### Dashboard Management```
"List all dashboards"
"Show me the Host Metrics dashboard details"

Service Analysis```

"List all services from the last 24 hours"
"What are the top operations for the paymentservice?"


#### Log Analysis```
"List all saved log views"
"Show me error logs for the paymentservice from the last hour"
"Search paymentservice logs for 'connection timeout' errors"
"Get error logs with FATAL severity"

Trace Analysis```

"Show me all available trace fields"
"Search traces for the apple service from the last hour"
"Get details for trace ID ball123"
"Check for error patterns in traces from the randomservice"
"Show me the span hierarchy for trace xyz789"
"Find traces with errors in the last 2 hours"
"Give me flow of this trace"
```

Tool Reference

list_metric_keys

Lists all available metric keys from SigNoz.

search_metric_keys

Searches for metrics by text query.
- Parameters: searchText (required) - Text to search for

list_alerts

Lists all active alerts from SigNoz.

get_alert

Gets details of a specific alert rule.
- Parameters: ruleId (required) - Alert rule ID

list_dashboards

Lists all dashboards with summaries (name, UUID, description, tags).
- Returns: Simplified dashboard information for better LLM processing

get_dashboard

Gets complete dashboard configuration.
- Parameters: uuid (required) - Dashboard UUID

list_services

Lists all services within a time range.
- Parameters:
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in nanoseconds (defaults to 24 hours ago)
- end (optional) - End time in nanoseconds (defaults to now)

get_service_top_operations

Gets top operations for a specific service.
- Parameters:
- service (required) - Service name
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in nanoseconds (defaults to 24 hours ago)
- end (optional) - End time in nanoseconds (defaults to now)
- tags (optional) - JSON array of tags

get_alert_history

Gets alert history timeline for a specific rule.
- Parameters:
- ruleId (required) - Alert rule ID
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start timestamp in milliseconds (defaults to 24 hours ago)
- end (optional) - End timestamp in milliseconds (defaults to now)
- offset (optional) - Offset for pagination (default: 0)
- limit (optional) - Limit number of results (default: 20)
- order (optional) - Sort order: 'asc' or 'desc' (default: 'asc')

list_log_views

Lists all saved log views from SigNoz.
- Returns: Summary with name, ID, description, and query details

get_log_view

Gets full details of a specific log view by ID.
- Parameters: viewId (required) - Log view ID

get_logs_for_alert

Gets logs related to a specific alert automatically.
- Parameters:
- alertId (required) - Alert rule ID
- timeRange (optional) - Time range around alert (e.g., '1h', '30m', '2h') - default: '1h'
- limit (optional) - Maximum number of logs to return (default: 100)

get_error_logs

Gets logs with ERROR or FATAL severity within a time range.
- Parameters:
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)
- service (optional) - Service name to filter by
- limit (optional) - Maximum number of logs to return (default: 100)

search_logs_by_service

Searches logs for a specific service within a time range.
- Parameters:
- service (required) - Service name to search logs for
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)
- severity (optional) - Log severity filter (DEBUG, INFO, WARN, ERROR, FATAL)
- searchText (optional) - Text to search for in log body
- limit (optional) - Maximum number of logs to return (default: 100)

get_trace_field_values

Gets available field values for trace.
- Parameters:
- fieldName (required) - Field name to get values for (e.g., 'service.name', 'http.method')
- searchText (optional) - Search text to filter values

search_traces_by_service

Searches traces for a specific service.
- Parameters:
- service (required) - Service name to search traces for
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)
- operation (optional) - Operation name to filter by
- error (optional) - Filter by error status (true/false)
- minDuration (optional) - Minimum duration in nanoseconds
- maxDuration (optional) - Maximum duration in nanoseconds
- limit (optional) - Maximum number of traces to return (default: 100)

get_trace_details

Gets trace information including all spans and metadata.
- Parameters:
- traceId (required) - Trace ID to get details for
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)
- includeSpans (optional) - Include detailed span information (true/false, default: true)

get_trace_error_analysis

Analyzes error patterns in traces.
- Parameters:
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)
- service (optional) - Service name to filter by
- Returns: Traces with errors, useful for identifying patterns and affected services

get_trace_span_hierarchy

Gets trace span relationships and hierarchy.
- Parameters:
- traceId (required) - Trace ID to get span hierarchy for
- timeRange (optional) - Time range like '2h', '6h', '2d', '7d'
- start (optional) - Start time in milliseconds (defaults to 24 hours ago)
- end (optional) - End time in milliseconds (defaults to now)

signoz_execute_builder_query

Executes a SigNoz Query Builder v5 query.
- Parameters: query (required) - Complete SigNoz Query Builder v5 JSON object
- Documentation: See SigNoz Query Builder v5 docs

signoz_query_helper

Helper tool for building SigNoz queries.
- Parameters:
- signal (optional) - Signal type: traces, logs, or metrics
- query_type (optional) - Type of help: fields, structure, examples, or all
- Returns: Guidance on available fields, signal types, and query structure

Time Format

Most tools support flexible time parameters:

Recommended: Time Ranges

Use the timeRange parameter with formats:
- '30m' - Last 30 minutes
- '2h' - Last 2 hours
- '6h' - Last 6 hours
- '2d' - Last 2 days
- '7d' - Last 7 days

The timeRange parameter automatically calculates the time window from now backwards. If not specified, most tools default to the last 24 hours. You can also specify time in milliseconds and nanoseconds

Response Format

All tools return JSON responses that are optimized for LLM consumption:
- List operations: Return summaries to avoid overwhelming responses
- Detail operations: Return complete data when specific information is requested
- Error handling: Structured error messages for debugging

🔧 Configuration & Deployment

Environment Variables

Variable Description Required
SIGNOZ_URL SigNoz instance URL Yes
SIGNOZ_API_KEY SigNoz API key (get from Settings → Workspace Settings → API Key in SigNoz UI) Yes
LOG_LEVEL Logging level: info(default), debug, warn, error No
TRANSPORT_MODE MCP transport mode: stdio(default) or http No
MCP_SERVER_PORT Port for HTTP transport mode Yes only when `TRANSPORT_MODE=http

🤝 Contributing

We welcome contributions!

Development Setup

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests
  5. Submit a pull request

Code Style

  • Follow Go best practices
  • Use meaningful variable names
  • Add comments for complex logic
  • Ensure proper error handling

Made with ❤️ for the observability community

常见问题

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

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

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

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

Signoz MCP Server Fc3aa65b 收费吗?

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

Signoz MCP Server Fc3aa65b 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

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

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

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

资料显示约 19 个工具;能力标签包括 可观测性、日志分析、Go、Claude。具体工具清单以官方文档为准。

热门专题

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

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