Use Polar Signals MCP with
Sokko.
Connect Polar Signals MCP and tell Sokko what to do. It runs the actions you ask for and reacts to what happens. No workflows, no code.
Works with 1,000+ tools · No code required
Actions
Everything Sokko can do in Polar Signals MCP
Every Polar Signals MCP action Sokko can run. Ask for one in a sentence and it's done.
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 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 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 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.
Get connected
Live in your Slack in two minutes.
No workflows to wire up. Turn on the tools you already use, and your agent gets to work.
Add to Slack
1
Add Sokko to Slack
One click from the Slack marketplace. Your whole team gets Sokko at once.
2
Connect your tools
Sokko works with 1,000+ apps and any MCP server.
Martin
9:53 AM
@Sokko
What can you do with Polar Signals MCP?
3
Put Sokko to work
@mention Sokko in any channel and it gets going. Minutes, not a weekend.
Questions, answered.
Sokko is an AI assistant that lives in your Slack. Connect your apps, ask for what you need in plain language, and Sokko takes the work off your plate.
Sign up to Sokko, ask Sokko to connect to Polar Signals MCP, and approve the connection when prompted. From then on you can ask Sokko to do things in Polar Signals MCP whenever you need.
No. There's nothing to build or configure. You ask Sokko in Slack the same way you'd ask a colleague, and Sokko handles the rest.
Yes. Ask once and tell Sokko when to repeat it, like every Monday at 9am, and it becomes a routine that runs without you.
Read and act on data in Polar Signals MCP, and trigger workflows when something changes there. Tell Sokko the outcome you want and it handles the rest.
Yes. Sokko connects to 1,000+ apps and any MCP server, so you can ask for tasks that span Polar Signals MCP and the rest of your stack in a single request.