Skip to main content
GetWhys plugs into Claude, Cursor, Typeface, and the agents your team has built. Buyer intelligence becomes the layer behind every AI workflow. Your team already lives in Claude, Cursor, Typeface, Copilot, and the AI agents they’ve built themselves. The GetWhys MCP server makes GetWhys show up wherever they already work, so buyer intelligence isn’t a tab someone opens when they remember to — it’s the layer every tool in the stack draws from automatically, every time. This is the validation layer extended across your entire AI stack.

​
What MCP unlocks

Through MCP, any AI tool your team uses can call GetWhys directly. Personas, messaging frameworks, brand voice, and the buyer signal database become callable resources inside Claude, Cursor, Typeface, and any custom agent. A few patterns:
  • AI content generation with built-in buyer context. Your team’s content tool calls into GetWhys for the persona and messaging framework before it writes a draft. The output starts grounded instead of starting from scratch.
  • Agentic research that pulls real interviews. When an agent is researching a competitive teardown or a market scan, it queries GetWhys for primary buyer research instead of relying on general model knowledge.
  • Persona-aware content scoring inside other tools. Tools your team has built can call GetWhys to score copy mid-draft against a target persona — before it ships, not after.
  • Always-on buyer intelligence in Slack, your CRM assistant, your internal agents. One source of truth, accessible anywhere your team works.

​
Tools exposed through MCP

​
For PMM and marketing leaders

MCP is how you make your judgment scale. Your defined personas, your messaging framework, and your brand voice become the constraints that every AI workflow in the company runs against — automatically. Sellers don’t need to know that the proposal they built in Claude was improved by GetWhys. They just get a better proposal. Your PMMs don’t need to change how they work. Buyer intelligence sits behind every tool they already use. You set the standard once. GetWhys enforces it everywhere your team builds.
For account setup, tokens, client configuration, the org skill install, and Slack, see MCP integration documentation