> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Overview

> GetWhys plugs into Anthropic Claude, OpenAI Chat, Gemini, Typeface, Writer, Microsoft 365 Copilot, custom agents, and your AI stack. Buyer intelligence becomes the layer behind every AI workflow.

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](/integrations/mcp-setup) first for the endpoint, auth options, and token generation — then come back here.

### Assistants

<CardGroup cols={2}>
  <Card title="Claude.ai / Desktop / Code" icon="comments" href="/integrations/mcp-claude">
    Custom connector, Claude Code CLI, and the GetWhys skill.
  </Card>

  <Card title="Claude Tag (Slack)" icon="slack" href="/integrations/mcp-claude-tag">
    Access bundles and plugins for `@Claude` in Slack — not the GetWhys Slack bot.
  </Card>

  <Card title="ChatGPT" icon="message" href="/integrations/mcp-chatgpt">
    Developer Mode connectors in OpenAI Chat.
  </Card>

  <Card title="Gemini Enterprise" icon="sparkles" href="/integrations/mcp-gemini">
    Custom MCP Server data store in Google Cloud.
  </Card>

  <Card title="Microsoft 365 Copilot" icon="microsoft" href="/integrations/mcp-microsoft-copilot">
    Federated connector for Microsoft 365 Copilot Chat.
  </Card>
</CardGroup>

### Content platforms

<CardGroup cols={2}>
  <Card title="Writer" icon="pen-nib" href="/integrations/mcp-writer">
    WRITER Agent via Writer's MCP gateway.
  </Card>

  <Card title="Typeface" icon="font" href="/integrations/mcp-typeface">
    Typeface MCP via OAuth.
  </Card>
</CardGroup>

### Other

<CardGroup cols={2}>
  <Card title="Generic MCP client" icon="plug" href="/integrations/mcp-generic">
    Cursor, custom agents, or any other MCP-compatible app.
  </Card>

  <Card title="MCP Setup" icon="gear" href="/integrations/mcp-setup">
    Shared endpoint, auth methods, token generation, and security.
  </Card>
</CardGroup>

## 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`):

| Tool                           | What it does                                                                                                                                                                                                                                                                     |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `whoami`                       | Returns who is connected: your user and organization when you signed in with OAuth, or organization-only context when using an org token or OAuth MCP Connector.                                                                                                                 |
| `list_personas`                | Lightweight index of non-archived Personas (`persona:<handle>` and name). Use before `get_persona` or `score_content`.                                                                                                                                                           |
| `get_persona`                  | Full detail for one Persona by `persona:<handle>` — challenges, motivations, KPIs, stakeholders, watering holes, job titles, and related fields.                                                                                                                                 |
| `get_all_personas`             | Full detail for every non-archived Persona in one call. Use when you need the whole set; for one target persona, prefer `list_personas` + `get_persona`.                                                                                                                         |
| `list_messaging_frameworks`    | Index of Messaging Frameworks (`id`, `title`, `description`). Use to disambiguate names before `get_messaging_framework`.                                                                                                                                                        |
| `get_messaging_framework`      | Full content of one Framework by `id` or exact `title`.                                                                                                                                                                                                                          |
| `get_all_messaging_frameworks` | Full content of every Framework — the default path for on-brand content generation.                                                                                                                                                                                              |
| `get_brand_voice`              | Brand Voice characteristics with do's and don'ts. Pair with `get_all_messaging_frameworks` when drafting publishable copy.                                                                                                                                                       |
| `query_market_research`        | **One focused buyer-research question per call.** Returns a synthesized, evidence-grounded answer from GetWhys interviews and your uploaded documents, with inline grounding markers, a **GetWhys Sources** summary, and a `view_in_getwhys` link.                               |
| `get_market_research`          | **Free-form research brief** (single or multiple asks). GetWhys may decompose it into parallel lookups and return one synthesized answer with the same sourcing pattern as above.                                                                                                |
| `score_content`                | Score marketing copy against a `persona:<handle>`. Returns an overall 0–100 score, dimensional breakdown, recommendations, and — when configured — `brand_voice_match` and `framework_match` (plus optional `specified_framework_match` when you pass `messaging_framework_id`). |

<Info>
  **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.
</Info>

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.