pyroscope-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYROSCOPE_BASE_URL | No | Pyroscope server URL | http://localhost:4040 |
| PYROSCOPE_TENANT_ID | No | Multi-tenant org ID (X-Scope-OrgID header) | |
| PYROSCOPE_AUTH_TOKEN | No | Bearer token (Grafana Cloud or Azure AD) | |
| PYROSCOPE_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pyroscope_render_profileB | Query the legacy /pyroscope/render endpoint for flamegraph and timeline data. |
| pyroscope_label_namesC | List available label names via Connect API. |
| pyroscope_label_valuesC | List label values for a given label name via Connect API. |
| pyroscope_profile_typesC | List available profile types via Connect API. |
| pyroscope_seriesC | Return profile series for given matchers via Connect API. |
| pyroscope_connect_queryC | Execute any Pyroscope Connect query endpoint with a raw JSON request body. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: executing raw queries, listing labels, label values, profile types, rendering profiles, and retrieving series. No two tools have overlapping functionality.
All tool names follow a consistent 'pyroscope_{verb_or_noun}' pattern in snake_case, making the set predictable and easy to navigate.
Six tools is a reasonable count for a profiling API client, covering essential operations without being too sparse or bloated. Slight under-coverage is possible but acceptable.
The set covers key Pyroscope API operations: querying, metadata (labels, profile types), and data retrieval (render, series). Minor gaps like specific profile operations or CRUD might exist but are not critical for typical usage.