The Yogi MCP server is the hosted service that gives AI tools secure access to your consumer feedback data in Yogi. It connects your account directly to your AI assistant through the Model Context Protocol (MCP), an open standard for AI integrations.
It brings the same consumer feedback analysis that powers Ask Yogi into the tools your team already works in — so anyone with a Yogi login can query their data in plain language, without opening the Yogi app. And because Yogi sits alongside your other connected tools (CX platforms, sales systems, ad platforms, CRMs, project management tools, and more), a single prompt can combine consumer voice with the rest of your team's data.
Access
Yogi MCP is available to all Yogi users — you'll sign in with your existing Yogi account, and you'll only ever see the data your account already has access to.
See below for detailed how-to documentation on how to set up the Yogi connector:
Yogi is a standard MCP server, so most tools that support MCP can connect. Setup varies. Contact us for further assistance: support@meetyogi.com
What can you do with the Yogi MCP?
On its own
If you know how to prompt Ask Yogi, you already know how to prompt this. Try:
"Show me the top themes for [product] in the last month."
"Give me 10 verbatims where customers complained about texture."
"Compare average rating for [product] before and after the formula change in April."
"Draft an executive summary detailing overall performance and the top 3 positive and negative drivers for our brands in June 2026. Exclude promotional reviews."
With your other connectors
The real unlock is when Yogi sits alongside your team's other tools — CX, ads, sales, CRM, retail data, and more. A single prompt can combine consumer voice with the rest of your stack.
Examples by team:
Brand managers: "We reformulated [product] in April. Compare sentiment and review themes before and after, and correlate with any change in return rate from our ecomm platform."
Marketing: "CPA on [product] campaign jumped 40% this week. Look at sentiment and theme shifts in Yogi — is there a product story behind it?"
Customer success / CX: "Scan reviews this week for any emerging complaint themes we haven't seen in tickets yet. For anything you find, draft a CX macro agents can use and set up auto-tagging in our CX platform so incoming tickets on the same theme route to the right queue."
R&D: "Are any negative themes or keywords emerging on our [product] this quarter that we should investigate? Cross-reference anything you find with production batches, ingredient supplier changes, and manufacturing incidents in our ops system to see if there's a source."
Sales / retail: "I have a Whole Foods buyer meeting on Thursday. Pull top positive verbatims and rating trends for [product line], and layer in sell-through from our retail data."
Executive / cross-functional: "Give me a Monday brief: top emerging themes in reviews last week, sales pacing vs. plan, and any CX volume anomalies. Send the brief via Slack to my team."
Tips for getting the best results
Name Yogi in your prompt. Saying "in Yogi" or "using Yogi" informs Claude what to reach for — otherwise, with multiple connectors installed, it has to guess.
Be specific about products, timeframes, and filters — vague prompts get vague answers.
Iterate in the same conversation — change filters or swap products without starting over.
For cross-tool questions, make sure the other connector is installed in Claude. Yogi can only reason across tools that are actually connected in your workspace.
Available tools
For a full list of tools the Yogi MCP exposes, see this article.
What's coming soon
Actions in Yogi from your AI assistant — create dashboards, draft alerts, spin up agents
Broader support across AI tools, including simpler setup for enterprise-managed environments