New MCP connectors let Zoë read the context your stack already holds, and act in the systems your team already uses.
If you're the one who owns your data stack, you know the fear about adopting a new agent: "Great, now I have to maintain yet another context layer."
It's a fair concern. Your business logic isn't in one place (impossible in any large company), it's scattered across platforms, each holding definitions someone fought hard to get right.
Drop in an agent that starts from zero and its definitions will drift away from your other tools. You're stuck with either wrong answers or a massive amount of manual synchronization, and both of those land on your desk. What if the agent played nicely with your existing data context?
Today, we're launching MCP connectors for Zoë.
Zoë connects directly to your existing tools as an MCP client, reads the context that's already there, and sets herself up. No rebuild. The years of logic locked in your other tools becomes the starting point.
Then the loop closes:
Zoë uses the same definitions across analytics and operations. And every question makes the next one smarter.
Data → Analysis → Insight → Action → Behavior ↺ back to Data
Each one starts with analysis Zoë already does well, and ends with an action she writes back through MCP. The final row is the general pattern: if you've automated it, Zoë can trigger it from an insight.
|
Use Case |
Action Zoë Takes |
Example Systems |
|
Sales planning / Sales ops |
Builds territory design, segmentation, and account scoring from firmographic and CRM data, then writes the resulting account assignments and priorities back into the CRM. |
ZoomInfo, Pipedrive |
|
Customer success / Retention |
Scores at-risk accounts from product telemetry, engagement, and CSM notes, then creates the next-best-action task and health flag directly for the CSM to work that week. |
Gainsight |
|
Revenue / Subscriptions |
Detects churn signals, MRR movement, and failed-payment patterns, then actions the subscription or flags the account for intervention. |
Stripe |
|
Product & Delivery |
Reads delivery, velocity, and incident signals, then creates and triages the issues that need attention. |
Linear, Jira, GitHub |
|
Trigger any business workflow |
Detects a signal in the data and fires the workflow your team already runs: alerts, escalations, provisioning, approvals, multi-step automations. If you've automated it, Zoë can trigger it from an insight. |
Azure Logic Apps, internal APIs |
As an admin, you control all of it: which connections exist, which tools Zoë can call on each one, and when credentials get rotated. Set it up in Workspace Settings → Extensions → MCP.
In short: Zoë moves from a place you go to read numbers, to a teammate who reads the numbers, acts on them across your stack, and closes the loop.