Skip to main content
Your team already lives in Anthropic Claude, OpenAI Chat, Gemini, Typeface, Writer, Microsoft 365 Copilot, and custom agents. 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.

​
Pick your client

Know which app you’re connecting? Jump straight to that guide. If you’re new to GetWhys MCP, skim MCP Setup first for the endpoint, auth options, and token generation — then come back here.

​
Assistants

Claude.ai / Desktop / Code

Custom connector, Claude Code CLI, and the GetWhys skill.

Claude Tag (Slack)

Access bundles and plugins for @Claude in Slack — not the GetWhys Slack bot.

ChatGPT

Developer Mode connectors in OpenAI Chat.

Gemini Enterprise

Custom MCP Server data store in Google Cloud.

Microsoft 365 Copilot

Federated connector for Microsoft 365 Copilot Chat.

​
Content platforms

Writer

WRITER Agent via Writer’s MCP gateway.

Typeface

Typeface MCP via OAuth.

​
Other

Generic MCP client

Cursor, custom agents, or any other MCP-compatible app.

MCP Setup

Shared endpoint, auth methods, token generation, and security.

​
What MCP unlocks

Through MCP, any AI tool your team uses can call GetWhys directly. Personas, messaging frameworks, brand voice, and the research interview database become callable resources across your stack. 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

GetWhys registers these tools on the MCP server (names match what your client shows in tools/list):
Buyer research tool: Each connection exposes either query_market_research or get_market_research, not both. Which one you see depends on your organization’s GetWhys configuration.
Research and persona tools return synthesized answers — not raw interview transcripts or full uploaded file contents. That boundary is intentional so buyer evidence can flow into external AI tools safely.

​
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 their AI tool 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.