Skip to main content
Connect GetWhys to Writer as a custom MCP connector. Your team can then use GetWhys research, personas, messaging frameworks, brand voice, and content scoring from WRITER Agent.
Writer’s MCP connectors currently work in WRITER Agent only. They don’t support Agent Builder, no-code agents, or API integrations.

​
Before you start

This setup requires two roles. They can be held by the same person:
  • A GetWhys admin to generate OAuth credentials
  • A Writer Org Admin or IT Admin to configure the connector in AI Studio

​
Connect GetWhys

1

Generate GetWhys OAuth credentials

Generate an OAuth MCP Connector in GetWhys with a label such as writer. Copy the OAuth Client ID and OAuth Client Secret. GetWhys shows the secret only once.On the connector, click Edit URIs and add the redirect URI for your Writer region:
2

Create the custom connector

In Writer AI Studio, open Connectors & Tools and select Create custom connector. Choose MCP server, then enter:Select Next.
3

Configure access and OAuth

Keep the default profile name or choose one your team will recognize. Give access to all teams or select specific teams, then configure authentication:Complete the connection flow and enable the GetWhys tools you want WRITER Agent to use.
The connector is now available to the teams you selected. Because it uses organization-level OAuth, teammates don’t sign in to GetWhys individually.

​
Verify the connection

In WRITER Agent, select + → Connectors and choose GetWhys. Then ask: “Who am I in GetWhys?” If Writer returns your GetWhys organization, you’re connected.

​
Try it

Ask WRITER Agent to pull buyer research, apply a persona or messaging framework, check brand voice, or score a draft. For example:
Pull the top three objections enterprise buyers raise about [category] from GetWhys, then revise this landing page draft to address them.

​
Troubleshooting

Tool calls return an authentication error — confirm the OAuth client ID and secret, then verify that the correct Writer redirect URI appears under Edit URIs in GetWhys. 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. You can’t generate OAuth credentials in GetWhys — ask a GetWhys admin to create the connector for you.