Polar in Height: the work written from the numbers, not from memory.
Height is where the work gets assigned. Connect Polar and an agent reads your governed metrics, then writes the weekly plan and the action items straight into your lists, tagged by priority, owner and channel, on a schedule. Polar is the numbers; Height is where they turn into work.
/Setup Guide
How to Connect Height to Polar.
A Polar account with your stack connected, a Height workspace, and an agent with the Polar MCP and your Height.
01 · What you need
A Polar account with your stack
A Polar account with Shopify and your sources connected. Height gets the same governed metrics your dashboards do.
Connect your data →A Height workspace
A Height workspace and one list or doc where the plan and the action items will land. Start with a single weekly list.
Open Height →An agent with both connectors
An assistant (like Claude) with the Polar MCP and Height connected, so it can read your data and create the tasks in one flow.
02 · Connect Polar and Height to your agent
1
Give your agent the Polar MCP ~2 min
Governed metrics, first-party and sourced.
Connect the Polar MCP to your assistant. It reads your governed semantic layer,
net sales, blended CAC, contribution margin, so every task it writes is grounded in a real number.2
Connect your Height ~2 min
The list it will write to.
1
Point the agent at the Height list or doc it should write to, a weekly planning list, or a growth backlog.
2
It uses two connectors together: Polar for the numbers, Height to turn them into assigned work.
3
Draft and schedule the payoff
Tasks, on a cadence.
Ask once for the weekly plan or for action items tagged by priority, owner and channel. Put it on a schedule and the list fills itself every Monday, before the standup.
push this week's action items into our Height list
create a task for any channel whose CAC moved more than 15%
create a task for any channel whose CAC moved more than 15%
Side by side
Height holds the work. Polar decides what the work should be.
Tasks and lists live in Height, and the numbers that should drive them live somewhere else, so the weekly plan gets written from memory. Polar supplies the governed figures and an agent turns them into tagged, assignable work.
Height on its ownon its own
+Height with Polarblended
The plan is written from memory, not from the data.
Tasks generated from Polar's governed numbers.
Every metric quoted in a task is looked up by hand.
Each item cites the metric that created it.
Someone has to spot a problem before it becomes work.
A task appears when a metric crosses your threshold.
The list depends on whoever filled it in.
The same inputs and the same definitions, every week.
The Gap
The connector is only half of it.
Your agent reads Polar's governed metrics over MCP and turns them into work inside Height: a filled weekly list, tasks tagged by owner and channel, a review doc that cites its numbers. First-party and sourced, never remembered.
Height
the numbers & the list to fill
tasks, tagged and assigned