Skip to main content
Glama
mahigadamsetty

pyroscope-mcp

by mahigadamsetty
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

pyroscope-mcp

A read-only Model Context Protocol (MCP) server for Grafana Pyroscope. Lets AI assistants query continuous profiling data — flamegraphs, hotspot functions, memory allocations, label discovery — directly from any MCP-compatible client.

Note: This server is query-only. Profile ingestion is expected to be handled by your application profilers (Pyroscope SDKs, agents, or exporters).

Tools

Tool

Description

pyroscope_render_profile

Flamegraph + timeline data from /pyroscope/render

pyroscope_label_names

List all label names in a time range

pyroscope_label_values

List values for a given label (e.g. service_name)

pyroscope_profile_types

List available profile types (cpu, memory, goroutines…)

pyroscope_series

Fetch matching label sets for a selector

pyroscope_connect_query

Raw access to any /querier.v1.QuerierService/* endpoint

Related MCP server: Polar Signals Remote MCP

Prerequisites

  • Node.js 20+

  • A running Pyroscope instance (local, self-hosted, or Grafana Cloud)

Setup

git clone https://github.com/your-org/pyroscope-mcp
cd pyroscope-mcp
npm install
npm run build

Configuration

All settings are provided via environment variables:

Variable

Default

Description

PYROSCOPE_BASE_URL

http://localhost:4040

Pyroscope server URL

PYROSCOPE_AUTH_TOKEN

—

Bearer token (Grafana Cloud or Azure AD)

PYROSCOPE_TENANT_ID

—

Multi-tenant org ID (X-Scope-OrgID header)

PYROSCOPE_TIMEOUT_MS

30000

Request timeout in milliseconds

Copy .env.example to .env and fill in your values:

cp .env.example .env

Adding to MCP Clients

VS Code (GitHub Copilot)

Create or edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "pyroscope": {
      "type": "stdio",
      "command": "node",
      "args": ["${workspaceFolder}/dist/index.js"],
      "env": {
        "PYROSCOPE_BASE_URL": "http://localhost:4040"
      }
    }
  }
}

Then open the MCP: List Servers command in VS Code (Cmd+Shift+P) and start the server. Copilot Chat will automatically discover the tools.

For a global (user-level) config instead of per-workspace, add the same block to your VS Code settings.json under "mcp":

{
  "mcp": {
    "servers": {
      "pyroscope": {
        "type": "stdio",
        "command": "node",
        "args": ["/absolute/path/to/pyroscope-mcp/dist/index.js"],
        "env": {
          "PYROSCOPE_BASE_URL": "http://localhost:4040"
        }
      }
    }
  }
}

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "pyroscope": {
      "command": "node",
      "args": ["/absolute/path/to/pyroscope-mcp/dist/index.js"],
      "env": {
        "PYROSCOPE_BASE_URL": "http://localhost:4040",
        "PYROSCOPE_AUTH_TOKEN": ""
      }
    }
  }
}

Restart Claude Desktop. A hammer icon will appear in the chat input when the server is active.

On Windows, wrap the command:

{
  "mcpServers": {
    "pyroscope": {
      "command": "cmd",
      "args": ["/c", "node", "C:\\path\\to\\pyroscope-mcp\\dist\\index.js"],
      "env": {
        "PYROSCOPE_BASE_URL": "http://localhost:4040"
      }
    }
  }
}

Cursor

Open Cursor Settings → MCP and add a new server entry, or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pyroscope": {
      "command": "node",
      "args": ["/absolute/path/to/pyroscope-mcp/dist/index.js"],
      "env": {
        "PYROSCOPE_BASE_URL": "http://localhost:4040"
      }
    }
  }
}

Reload Cursor. The tools appear automatically in the Composer agent context.

Zed

Add to your Zed settings.json (open via Zed → Settings):

{
  "context_servers": {
    "pyroscope": {
      "command": {
        "path": "node",
        "args": ["/absolute/path/to/pyroscope-mcp/dist/index.js"],
        "env": {
          "PYROSCOPE_BASE_URL": "http://localhost:4040"
        }
      }
    }
  }
}

Any MCP-compatible client (generic stdio config)

{
  "mcpServers": {
    "pyroscope": {
      "command": "node",
      "args": ["/absolute/path/to/pyroscope-mcp/dist/index.js"],
      "env": {
        "PYROSCOPE_BASE_URL": "http://localhost:4040",
        "PYROSCOPE_AUTH_TOKEN": "your-bearer-token-if-needed",
        "PYROSCOPE_TENANT_ID": "your-org-id-if-needed"
      }
    }
  }
}

Example prompts once connected

  • "List all services sending profiles in the last hour."

  • "Show the hottest CPU functions for media-agent in the last 30 minutes."

  • "What is the memory allocation hotspot in api-gateway?"

  • "Compare CPU usage between worker-service and data-pipeline."

  • "What profile types are available for checkout-api?"

Notes

  • For multi-tenant Pyroscope, set PYROSCOPE_TENANT_ID or pass tenantId per tool call.

  • pyroscope_connect_query gives raw access to advanced endpoints:

    • /querier.v1.QuerierService/SelectMergeStacktraces

    • /querier.v1.QuerierService/SelectSeries

    • /querier.v1.QuerierService/Diff

  • For Grafana Cloud Pyroscope, set PYROSCOPE_BASE_URL to your stack URL and PYROSCOPE_AUTH_TOKEN to a service account token.

Query smoke test

  1. Start Pyroscope locally:

docker run -d --name pyroscope -p 4040:4040 grafana/pyroscope:latest

  1. Query label names from the last hour:

NOW_MS=$(($(date +%s)*1000))
START_MS=$((NOW_MS-3600000))
curl -sS -H 'Content-Type: application/json' \
  -d "{\"start\":$START_MS,\"end\":$NOW_MS}" \
  http://localhost:4040/querier.v1.QuerierService/LabelNames

  1. Query service names from the last hour:

NOW_MS=$(($(date +%s)*1000))
START_MS=$((NOW_MS-3600000))
curl -sS -H 'Content-Type: application/json' \
  -d "{\"name\":\"service_name\",\"start\":$START_MS,\"end\":$NOW_MS}" \
  http://localhost:4040/querier.v1.QuerierService/LabelValues
Install Server
F
license - not found
B
quality
C
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

Related MCP Servers

  • Signoz MCP Server

    DrDroidLab
    A
    license
    -
    quality
    D
    maintenance
    An MCP server that enables AI assistants to interact with Signoz observability platform, providing tools to query dashboards, metrics, traces, logs, and APM data with time range support.
    Last updated
    14
    MIT

  • Polar Signals Remote MCP

    polarsignals
    F
    license
    -
    quality
    D
    maintenance
    MCP server for Polar Signals Cloud continuous profiling platform, enabling AI assistants to analyze CPU performance, memory usage, and identify optimization opportunities in production systems.
    Last updated
    9

  • OpenObserve MCP Server

    mdfranz
    F
    license
    -
    quality
    F
    maintenance
    An MCP server that enables AI assistants to query and explore your OpenObserve observability data. Provides read-only access to logs, metrics, and traces for analysis and troubleshooting.
    Last updated
    5

View all related MCP servers

Related MCP Connectors

  • mcp-grafana

    An MCP server giving access to Grafana dashboards, data and more.

  • Arcjet

    An MCP server for Arcjet - the runtime security platform that ships with your AI code.

  • driflyte-mcp-server

    Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.

View all MCP Connectors

Latest Blog Posts

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/mahigadamsetty/pyroscope-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server