Polar Signals MCP lets engineering agents inspect continuous profiling projects and performance data to diagnose regressions and optimization opportunities.
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. claude.md or system prompt), prefer that one. Otherwise, ask the user which project to use.
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' column, shown only when such frames are present. Use this for a top-down picture of where time goes; 'query_profile_table' gives a flat ranked list and 'query_profile_sandwich' focuses on one function. Drill into a subtree with 'focus_path'. Same query syntax as 'query_profile_table'.
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'.
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 names.
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.
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 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 tool outputs. With symbolized=false, unsymbolized rows (no function_name) gain an 'address' column carrying their hex memory address.
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 strings when calling 'labels' or 'query_profile_table' - do not invent or shorten profile type names.
The Polar Signals MCP integration connects your Dench AI CRM directly to Polar Signals MCP, so agents can read and act on your Polar Signals MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
8 actions are available for agents to invoke on your behalf. Every call runs through Polar Signals MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Polar Signals MCP and click Connect — you'll authorize access through Polar Signals MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Polar Signals MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Polar Signals MCP integration connects your AI CRM to Polar Signals MCP, so AI agents can work with your Polar Signals MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Polar Signals MCP integration currently exposes 8 actions, including List projects, Query profile flamegraph, Query profile label values, Query profile labels, Query profile sandwich, and Query profile source. Agents invoke them on your behalf from chat or from automations.
No. You connect Polar Signals MCP from your Dench workspace using Polar Signals MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Polar Signals MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Polar Signals MCP connection from your workspace settings at any time.