Skip to main content
GetWhys MCP gives supported AI tools access to your organization’s buyer research, Personas, Messaging Frameworks, and Brand Voice. Your team can use the same GetWhys context without switching tools.

​
Pick your client

Choose your app below. If you’re new to GetWhys MCP, start with MCP Setup for the endpoint and authentication options.

​
Assistants

Claude.ai / Desktop

Organization connector and the GetWhys skill.

Claude Code

Local CLI setup with individual or organization OAuth.

Claude Tag (Slack)

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

ChatGPT

Developer Mode connectors in ChatGPT.

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, recommended OAuth setup, token fallback, and security.

​
What MCP unlocks

An MCP client can call GetWhys while you work. For example, it can:
  • Retrieve a Persona, Messaging Framework, or Brand Voice before drafting content.
  • Answer a focused research question using buyer interviews and uploaded documents.
  • Score a draft against a target Persona and return recommendations.

​
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.