Part of Grafana, not a vendor of its own. The four checks, setup and context cost live in the Grafana guide.

Part of the Grafana stack

Grafana Pyroscope and MCP

What it is

Grafana's continuous profiler. It samples what your processes spend CPU and memory on, so the question it answers is which function is expensive.

How an agent reaches it

The main Grafana MCP server, with four tools on by default. Nothing extra is needed beyond a Pyroscope datasource.

The tools that touch it

list_pyroscope_profile_types

Lists the profile types available in a datasource and time range, such as CPU or memory.

list_pyroscope_label_names

Lists the label keys found in profiles for that datasource and range.

list_pyroscope_label_values

Lists the values of one label key, to scope down to a process.

query_pyroscope

The unified query tool, fetching either profile data or metrics from Pyroscope.

Four tools, all on by default, counted from the captured tools/list for the Grafana MCP server. All four read; none writes.

The limit an agent runs into

Four tools, all reads, and no flame graph structure among them. query_pyroscope returns profile data or metrics, so an agent reasons about cost from a flat result rather than by walking a call tree.

What to do: Scope with the label tools before querying. What an agent can reach is also bounded by whatever retention the Pyroscope install keeps, which is a local setting rather than a connector one.

Reference

Tools

4, all on by default

All of them

Read. None writes

Unified query tool

query_pyroscope, for profiles or metrics

Call-tree navigation

None. No sandwich or flame graph tool

Bounded by

The Pyroscope install's own retention