Uptrace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPTRACE_URL | Yes | The URL of your Uptrace instance (e.g., https://uptrace.xxx) | |
| UPTRACE_API_TOKEN | Yes | Your Uptrace API auth token | |
| UPTRACE_PROJECT_ID | Yes | The numeric ID of your Uptrace project |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uptrace_search_spansA | Search spans with custom filters using Uptrace Query Language (UQL). Supports WHERE clauses, filters, and aggregations. Use 'where _status_code = "error"' to find error spans. |
| uptrace_get_traceB | Get all spans for a specific trace ID. Useful for debugging and understanding request flows. |
| uptrace_search_groupsA | Search and aggregate spans by groups. Supports GROUP BY operations and aggregations like count(), avg(), p99(), etc. |
| uptrace_search_servicesA | Search for services that have reported spans. Useful for discovering available services in the system. |
| uptrace_search_logsA | Search logs by text, severity, service name, or custom UQL query. Logs are represented as spans with _system = 'log:all'. |
| uptrace_get_query_syntaxA | Get UQL (Uptrace Query Language) syntax documentation. Returns operators, functions, examples, and common patterns for querying spans, logs, and metrics. |
| uptrace_get_alertB | Get details of a specific alert incident by ID. |
| uptrace_list_monitorsA | List all alerting monitors. Returns monitor IDs, names, types, and configuration. |
| uptrace_get_monitorC | Get details of a specific monitor by ID. |
| uptrace_list_dashboardsA | List all dashboards. Returns dashboard IDs and names. |
| uptrace_query_metricsA | Query metrics using UQL/PromQL-compatible syntax. Use this to retrieve metric values like CPU usage, request rates, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dimonb/uptrace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server