Setup guide · 10 minutes

Spin up the Polar Operator in a Claude Project.

A router brain plus a 52-agent catalog. After this setup, anyone with the Project link and the Polar Analytics connector enabled can run any agent - no code, no deploy.

01What you need

Account

Claude.ai with Projects

A plan that supports Projects + remote connectors (Pro, Team, or Enterprise).

Connector

Polar Analytics

An official Claude connector. One-click enable inside your Project.

Time

~10 minutes

Five steps. No code, no deploy, no infrastructure to manage.

02Setup, step by step

1

Create a new Claude Project

Projects are reusable workspaces. The Polar Operator lives as one Project, and anyone you share it with can run any of the 52 agents.

  1. Go to claude.ai/projects ↗ and click Create Project.
  2. Name it Polar Operator (or your brand's variant).
  3. Pick any model - the operator is tuned for Claude Sonnet 4.6 and above.
2

Paste the Custom Instructions

This is the router brain - the universal flow, output discipline, and edge-case handling. Copy the full block below and paste into the Project's Custom Instructions field.

~2k tokens · ~101 lines
Prompt
Loading…
3

Upload the 52-agent catalog as Project Knowledge

The system prompt knows the names; this file holds the per-agent specs (inputs, signals, expected impact). The operator reads it on demand when it picks an agent.

dtc-agents-polar-mcp-prompts.md
Download the catalog - 52 agents, ~75 KB
  1. Download dtc-agents-polar-mcp-prompts.md using the link above.
  2. In your Project, open the Project Knowledge panel.
  3. Drop the file in. Wait for indexing to finish.
  4. That's it - the router will search this file when picking the right agent.
4

Enable the Polar Analytics connector

Polar Analytics is an official Claude connector - no custom MCP URL, no extra config. One click and the operator can pull live data.

  1. Open your Project's connector panel.
  2. Find Polar Analytics in the directory and click Enable. Or open it directly: claude.ai/directory/connectors/polar-analytics ↗
  3. Authorize with your Polar workspace. Confirm it shows ✓ Connected.
  4. Disable any connectors you don't want this Project to reach (Slack, Notion, etc.) unless you want cross-system answers.
5

Test with the demo prompts

Open a fresh conversation in your Project and paste any of these. Reply defaults when the operator asks for inputs.

Pro tips

Make it your own

Brand voice

Append a "House style" section to the Custom Instructions ("write in [Brand]'s voice, lean concise, no emojis"). Affects only output, not routing.

Lock an attribution model

If your team always reports on linear or last_click, hard-code it in the system prompt to skip asking each run.

Pilot subset

Pilot with one team? Comment out non-relevant agents from the catalog list at the top of the system prompt - the router will only offer that subset.

Graduate winners

Once an agent gets used 5+ times a week, give it a dedicated Project - tighter prompt, faster, no router overhead.

That's the whole setup. Now run a decision.