Polar Signals MCP + Stream Deck
model-context-protocol · developer-tools · server-monitoring · 0 triggers · 8 actions
Polar Signals MCP lets engineering agents inspect continuous profiling projects and performance data to diagnose regressions and optimization opportunities. Add Polar Signals MCP to your Stream Deck workflows with guided setup for the connection details it needs.
- No code
- Free tier
- One Stream Deck press
- Pairs with OBS & Elgato tools
- OAuth & keys handled in-builder
Popular ways to use Polar Signals MCP
Add Polar Signals MCP to a workflow and pair it with a Stream Deck button to run it in one press — handy for model-context-protocol tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.
Browse all templatesTriggers & actions
Steps your workflow can perform 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. claude.md or system prompt), prefer that one. Otherwise, ask the user which project to use.
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' 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'.
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 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.
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 tool outputs. With symbolized=false, unsymbolized rows (no function_name) gain an 'address' column carrying their hex memory address.
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 strings when calling 'labels' or 'query_profile_table' - do not invent or shorten profile type names.
About Polar Signals MCP
Polar Signals MCP lets engineering agents inspect continuous profiling projects and performance data to diagnose regressions and optimization opportunities.
model-context-protocoldeveloper-toolsserver-monitoringanalytics
How to connect
1
Sign up for free
Create your Conductor Deck account: no credit card required.
2
Connect Polar Signals MCP
Follow the setup prompts for Polar Signals MCP. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
3
Build a workflow
Add a Polar Signals MCP action to your visual workflow canvas. Configure the options you need, then connect it to other steps.
4
Assign to Stream Deck
Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.
Frequently asked questions
- How do I connect Polar Signals MCP?
- Sign up for Conductor Deck, then add a Polar Signals MCP step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
- Is it free?
- Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
- What's the difference between a trigger and an action?
- A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.
Automate Polar Signals MCP with your Stream Deck
Sign up for free and start building Polar Signals MCP workflows in minutes.