Polar Signals MCP
for LuumenAI

Read continuous profiling data to find where the time actually goes

Ask why a service got slower and work from real profiles. Polar Signals MCP covers projects, profile types, labels, flame graphs, flat tables, sandwich views for a single function, and per-line source data. Every tool here is classified as a write, so calls are previewed, approved, and audited by default. Luumen authenticates with an API key.

Book a demoDownload Luumen

The Polar Signals MCP toolbox

8 tools: 0 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • WriteList projectsList all projects accessible to the current user. Approval by default
  • WriteQuery profile flamegraphReturn a flame graph as a breadth-first call tree. Approval by default
  • WriteQuery profile labelsGet available label names for a specific profile type. Approval by default
  • WriteQuery profile label valuesList the values a profiling label takes (e.g. Approval by default
  • WriteQuery profile sandwichShow the calling context around a specific function: which functions call it (callers) and which functions it calls (callees). Approval by default
  • WriteQuery profile sourceRetrieve per-line profiling data for a specific source file. Approval by default
  • WriteQuery profile tableQuery profiling data as a flat table of functions sorted by cumulative time. Approval by default
  • WriteQuery profile typesProfileTypes returns the list of available profile types. Approval by default

Questions

How does LuumenAI connect to Polar Signals MCP?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Polar Signals MCP on its own?

This connection exposes write actions such as list projects, query profile flamegraph, query profile labels, query profile label values, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Polar Signals MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task statusAffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved steps

Put Polar Signals MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a demoDownload Luumen