Skip to main content
GetWhys connects to Writer as a custom connector through Writer’s MCP gateway. Once connected, WRITER Agent can pull directly from your research interviews, buyer personas, messaging frameworks, and brand voice while your team drafts — and validate content with Message Testing before it ships.
Writer connectors currently work in WRITER Agent (the chat assistant) only. They don’t yet reach Writer’s Agent Builder, no-code agents, or API integrations. If your team’s content flows through those, reach out via Teams, Slack, Google Chat, or email [email protected] and we’ll figure out the right setup together.

​
Who does what

Setup takes two admins and about ten minutes:

​
Create the custom connector in Writer

Your Writer org admin does this once in Writer AI Studio:
  1. Navigate to Connectors & Tools
  2. Select Create custom connector
  3. Choose MCP server as the connector type
  4. Enter the GetWhys MCP server URL:
  1. Give it a name (GetWhys) and a description your team will recognize, e.g. “Buyer validation: research interviews, personas, messaging frameworks, brand voice, and message testing.”
  2. Select Next

​
Configure access and authentication

On the configure step:
  1. Choose who has access — all teams, or specific teams (your GTM and content teams are the natural starting point)
  2. Select API key as the authentication method, and enter:
    • Key name: Authorization
    • Key prefix: Bearer
    • Key value: the Organization MCP API Token from step 1
  3. Complete the connection flow
GetWhys now appears in your Writer org’s connected integrations, and the tools you enable are available to authorized users in WRITER Agent.
This is an org-wide connection — teammates don’t need to authenticate individually. The token grants the same workspace access as OAuth sign-in: personas, messaging frameworks, brand voice, and the research corpus.

​
Verify the connection

In WRITER Agent, ask the verify prompt: “Who am I in GetWhys?”

​
What your team can do in WRITER Agent

  • Ground drafts in real buyer language — pull pain points, objections, and direct quotes from research interviews while writing
  • Stay in persona — load buyer personas so copy speaks to the right audience
  • Apply positioning consistently — reference messaging frameworks instead of reinventing value props per draft
  • Validate before shipping — score drafts against a target persona with Message Testing and flag copy that drifts off brand voice
Try a prompt like:
Pull the top three objections enterprise buyers raise about [category] from GetWhys, then revise this landing page draft to address them.

​
Troubleshooting

The connector saves but tool calls fail with an auth error — the token may have been revoked or mistyped. Generate a fresh token and update the key value in the connector’s configuration. Users don’t see GetWhys in WRITER Agent — check the connector’s team access settings in AI Studio, and confirm the tools are enabled in the connector configuration. “MCP API Tokens” card is missing in GetWhys — you may not have the required permissions. Contact your workspace owner, or reach out via Teams, Slack, Google Chat, or email [email protected].