
The Claude Slack app now supports MCPs. Connect the Polar MCP and ask your ecommerce data anything right where your team already works.
Two things shipped in the same week.
Anthropic rolled out MCP support inside the Claude Slack app. MCPs are how Claude talks to real data. Up until now, if you wanted Claude in Slack, you got a generic chatbot that couldn't see anything beyond the channel it was in. No metrics. No numbers. No answers.
Polar already had an MCP. It's been live for months, running inside Claude, ChatGPT, n8n, Make, Cursor, Lovable, Manus anywhere an LLM needs clean ecommerce data. Our MCP ships a semantic layer, not a pile of API responses.
That means when Claude asks for blended ROAS, it gets a single reconciled number modeled across Meta, Google, TikTok, Klaviyo, and Shopify. Not five raw metrics and a prayer.
Put those two together and something simple happens. Your team can now ask Polar questions in Slack. In a DM with Claude. In a thread where someone just flagged that Meta spend looked weird. In #marketing while you're still drinking coffee.
No dashboard login. No app switching. No SQL. No "let me pull that up and get back to you."
The old pattern looked like this: someone asks a question in Slack → someone else opens Polar → they find the number → they paste it back into Slack → the thread has moved on and no one remembers the question.
The new pattern is: someone asks a question in Slack, and the answer shows up in Slack.
That's it. That's the whole thing. But it changes who can actually use your data.
Founders stop waiting on the analyst. Marketing leads stop pinging the ops lead for numbers they already know how to interpret. Agency PMs stop building one-off reports for questions a client will ask once and forget. The CS team finally has a way to pull a quick number mid-conversation without breaking the flow.
Here's what five minutes in Slack starts to look like:
None of those need a human to open Polar. All of them are the kinds of questions that get asked in Slack ten times a week and answered never.
Three pieces, all already live:
That's the whole architecture. Ask in Slack → Claude routes the query → the Polar MCP hits the semantic layer → you get an answer with real numbers.
The reason it's better than any of the alternatives uploading CSVs, running a raw Shopify MCP, or asking a chatbot to compute CAC by multiplying ad spend by the phase of the moon is the same reason Polar exists in the first place. Blended CAC, MER, POAS, CM3, LTV these are not columns in a table.
They are definitions, agreed upstream of the LLM, so the LLM never has to guess. When your finance team and your performance team both ask "what's our CAC right now," they get the same number. That's the semantic layer doing its job. More on that in Polar is the Ecommerce Connector for Claude (pillar article, link to follow).
Three steps, assuming you've never touched any of this before. Skip any step you've already done.
On a paid Claude plan (Pro, Max, or Team), open the Polar Analytics connector in Claude's Directory and add it to your account. On a Team plan, click Add to team; on a personal Pro or Max plan, click Connect directly.

You can also find it from your Claude account under Customize → Connectors. Click Connect, sign in to Polar, and authorize Claude. That's it no URL to copy, no manual configuration.


Full walkthrough with screenshots in Use Polar MCP in Claude.
If you're completely new to Polar and haven't connected data sources yet, the MCP setup will prompt you to connect at least one. The initial historical sync can take up to 24 hours you'll get an email when it's ready.
This is the official Anthropic app in the Slack directory. Your Slack admin may need to approve it depending on your org's app policy. Once installed, connect it to your Claude account.
Inside Slack, confirm the Polar connector is enabled for the Claude app. Then DM Claude directly, or @-mention it in a channel, and ask:

What were our top 5 products by net sales last month?
Claude will hit the Polar MCP, run a generate_report tool call against the semantic layer, and reply in Slack with the numbers. First time it runs, you'll approve the tool call. After that it's just chat.
One tip worth building into your workflow: when Claude returns a number, glance at the tool call details before you forward it to your CEO. Date ranges and chosen metrics are visible, and confirming them takes two seconds. Every LLM gets date math wrong sometimes. Polar's MCP now returns totals and timezone context inside each report so Claude has clear bounds, but a quick sanity check is a free habit.
A non-exhaustive menu of questions that work well, grouped by who typically asks them. Every metric below lives in Polar's modeled layer Claude pulls the consolidated number, not a reconstruction.
That last one matters. Claude can pull any Polar dashboard or report by name through the MCP. If your team already has a weekly exec dashboard built in Polar, you don't need to rebuild it in prompts just reference it.
The bigger picture: every operator is going to end up with Claude open somewhere. The question is whether their Claude can see their business.
We think Polar is the answer to that question for ecommerce. Your Shopify, Meta, Google, Klaviyo, Amazon, TikTok, Recharge, and every other source gets modeled once in Polar, and then shows up consistently, with the same definitions everywhere Claude operates.
Today, Slack.
Already shipped: Claude Desktop, Claude Web, Claude Code, Claude Cowork, Claude in Chrome, Claude in Excel. Up next: more agentic surfaces as Anthropic keeps shipping.
One connection, every surface.
That's the thesis, and Slack is the first of many proofs of it. Full version in Polar is the Ecommerce Connector for Claude
