Integration / Analytics & Data
Polar Signals MCP integration
Polar Signals MCP lets engineering agents inspect continuous profiling projects and performance data to diagnose regressions and optimization opportunities.
About Polar Signals MCP
Polar Signals MCP is a continuous profiling and performance monitoring service for engineering teams. Use it to find regressions and surface runtime optimization opportunities.
All integrations- Category
- Analytics & Data, Developer Tools & DevOps
- Connection
- API key
- Type
- Tool
- Actions
- 8
- Tags
- library
Example prompts
What you can ask Growf to do with Polar Signals MCP
- “Summarize top CPU hotspots last week”
- “List regressions across releases for auth-service”
- “Create optimization checklist for auth-service hotspots”
Available actions
8 actions your agents can run in Polar Signals MCP
List projects
List all projects accessible to the current user. IMPORTANT: Call this FIRST before using any other tools. Returns project IDs and names. You need a project ID for all other tool calls. If only one project is returned, use it automatically. If a project is specified in the user's instructions (e.g.…
Query profile flamegraph
Return a flame graph as a breadth-first call tree. Each row has id, parent (the parent row's id, -1 = a root), depth, cumulative, flat, function_name — rebuild the tree via the parent pointers. Unsymbolized frames (no function_name) instead carry their hex memory address in an extra 'address' colum…
Query profile labels
Get available label names for a specific profile type. Call this after 'profile_types' to discover what labels exist. You MUST use exact profile type strings from 'profile_types' output. Returns label names that can be used with 'values' and in 'query_profile_table' queries - do not invent label na…
Query profile label values
List the values a profiling label takes (e.g. the process names for the 'comm' label). These are label values used to filter queries — not the sampled values of the profile itself. Use it to discover valid filter values; only use label names from 'query_profile_labels'.
Query profile sandwich
Show the calling context around a specific function: which functions call it (callers) and which functions it calls (callees). Use this after 'query_profile_table' to drill into a specific function. The function_name should be an exact function name from 'query_profile_table' results.
Query profile source
Retrieve per-line profiling data for a specific source file. Returns line numbers with flat and cumulative sample counts — without returning the source code itself (read the file directly and correlate using line numbers).
Query profile table
Query profiling data as a flat table of functions sorted by cumulative time. Recommended workflow: first call 'list_projects', then 'profile_types', then 'labels', then 'values' to discover valid query components. Query syntax: 'profile_type{label="value"}' where all components come from previous t…
Query profile types
ProfileTypes returns the list of available profile types. IMPORTANT: Call 'list_projects' first to get a project ID. Profile types follow the format 'name:sample_type:sample_unit:period_type:period_unit[:delta]' (e.g. 'parca_agent:samples:count:cpu:nanoseconds:delta'). You MUST use these exact stri…
Put Polar Signals MCP to work inside Growf.
Connect it once and every workspace, agent and workflow can use it — securely, with your team in the loop.