Skip to main content
GetWhys connects to Typeface through Typeface’s MCP flow so your team can pull buyer research and positioning context directly into content workflows grounded in Typeface.
Typeface MCP uses OAuth. You don’t need an Organization MCP API Token for the standard Typeface flow unless Typeface exposes an admin-level custom auth option in your environment.
Complete the shared steps in MCP Setup first (endpoint and auth overview).

​
Connect with GetWhys OAuth

  1. In Typeface, open the MCP / integrations flow for connecting an external MCP-compatible tool or service.
  2. Choose to add a new MCP connection.
  3. Enter the GetWhys MCP server URL:
  1. When prompted for authentication, choose OAuth.
  2. Sign in with your GetWhys account and approve the connection.
Once connected, Typeface can discover the GetWhys tools your account has access to.

​
Verify

Ask Typeface the verify prompt: “Who am I in GetWhys?”

​
Troubleshooting

The MCP connection screen asks for fields that don’t match this guide — Typeface is iterating on its MCP UI. If you see a custom auth variant instead of OAuth, reach out via Teams, Slack, Google Chat, or email [email protected] and we’ll help map the fields. The connection succeeds but GetWhys context doesn’t appear where you expect — confirm you’re on the Typeface surface that supports MCP, and reconnect if needed so Typeface refreshes the available tools and accounts.