SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Polar Signals MCP to Claude

Connect Claude Web, Desktop and Cowork to Polar Signals MCP. Summarize top cpu hotspots last week, list regressions across releases for auth-service, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Polar Signals MCP logoPolar Signals MCP
Api Key

Polar Signals MCP is a continuous profiling and performance monitoring service for engineering teams. Use it to find regressions and surface runtime optimization opportunities.

8 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Polar Signals account to Claude via Composio Connect, enabling it to summarize top CPU hotspots last week, list regressions across releases for auth-service, create optimization checklist for auth-service hotspots, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Polar Signals MCP with

ChatGPTHermesAtomic Agent

Connecting Polar Signals to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Polar Signals account

Back in Claude, ask it to connect to Polar Signals or give it any Polar Signals-related task.

For example, ask Claude to:

  • "Summarize top CPU hotspots last week"
  • "List regressions across releases for auth-service"
  • "Create optimization checklist for auth-service hotspots"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Polar Signals account is ready to use.

What is the Polar Signals Claude Connector, and what's possible with it?

The Polar Signals MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Polar Signals account. It provides structured and secure access so your agent can perform Polar Signals operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Polar Signals?

The connector can show as connected, but Claude must use it in each Polar Signals conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Polar Signals again.

2. Why does Claude show an MCP server error before Polar Signals connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Polar Signals.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Polar Signals.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Polar Signals authorization link not work?

The Composio connector is one server. Your Polar Signals account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Polar Signals connection.
  • Composio creates a fresh Polar Signals authorization link.
  • Open that link in your browser and finish the Polar Signals sign-in.

4. Why do Polar Signals actions fail after they worked before?

The Polar Signals connection can expire or lose permission.

  • Ask Claude to inspect the Polar Signals connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Polar Signals account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Polar Signals.
  • If the action still fails with a permission error, check that the connected account has that permission in Polar Signals itself.

5. How do I switch to a different Polar Signals account?

Claude can manage the Polar Signals connection for you.

  • Ask Claude to disconnect or delete the current Polar Signals account.
  • Ask Claude to connect Polar Signals again.
  • Open the new Composio authorization link for Polar Signals.
  • Sign in with the other Polar Signals account in the browser.
  • After the account connects, ask Claude to retry the Polar Signals task.

6. Why is my Polar Signals connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Polar Signals connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Polar Signals tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Polar Signals.
TOOLS

Supported Tools

Every Polar Signals MCP action and event your agent gets out of the box.

List projects

List all projects accessible to the current user.

Query profile flamegraph

Return a flame graph as a breadth-first call tree.

Query profile labels

Get available label names for a specific profile type.

Query profile label values

List the values a profiling label takes (e.

Query profile sandwich

Show the calling context around a specific function: which functions call it (callers) and which functions it calls (callees).

Query profile source

Retrieve per-line profiling data for a specific source file.

Query profile table

Query profiling data as a flat table of functions sorted by cumulative time.

Query profile types

ProfileTypes returns the list of available profile types.

FRAMEWORKS

How to build Polar Signals MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Polar Signals MCP with ChatGPT

Hermes logo

Hermes

Use Polar Signals MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Polar Signals MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone Polar Signals MCP server, the agents and LLMs can only access a fixed set of Polar Signals tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Polar Signals and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Polar Signals tools.

Yes, absolutely. You can configure which Polar Signals scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Polar Signals data and credentials are handled as safely as possible.

Start with Polar Signals MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Polar Signals MCP tool your agent needs.Free to start.

Start building