Skip to main content
Connect GetWhys through Typeface’s MCP integration. Your team can then use GetWhys buyer research and positioning context in Typeface content workflows.
Typeface’s standard MCP flow uses OAuth, so you don’t need an MCP API token. Some environments may offer an admin-level custom authentication option.
Review MCP Setup first for the shared endpoint and authentication overview.

​
Connect GetWhys with OAuth

  1. In Typeface, open the MCP or integrations flow for connecting an external MCP-compatible tool or service.
  2. Add a new MCP connection.
  3. Enter the GetWhys MCP server URL:
  1. When Typeface asks how to authenticate, choose OAuth.
  2. Sign in to your GetWhys account and approve the connection.
Once connected, Typeface discovers the GetWhys tools available to your account.

​
Verify the connection

Ask Typeface: “Who am I in GetWhys?”

​
Troubleshooting

The MCP connection screen doesn’t match this guide — Typeface may show a different MCP setup flow in your environment. If you see custom authentication instead of OAuth, contact [email protected] and we’ll help map the fields. GetWhys context doesn’t appear after connecting — confirm that you’re using a Typeface surface that supports MCP. If needed, reconnect so Typeface refreshes the available tools and accounts.