Recommended: connect with GetWhys OAuth
1. Enable Developer Mode
- In ChatGPT, open Settings → Security and login
- Turn on Developer mode
2. Create a developer-mode app / connector
- Open Settings → Plugins (or go to chatgpt.com/plugins)
- Select the + button to create a new developer-mode app
- Fill in:
- Name:
GetWhys - Description: e.g. “Buyer validation: research interviews, personas, messaging frameworks, brand voice, and message testing.”
- MCP server URL:
- Name:
- Set authentication to OAuth (ChatGPT’s preferred method for secured MCP servers)
- Confirm you trust the application and click Create
- Complete the GetWhys sign-in / authorize flow when prompted
Alternative: org-wide via token (query string)
If your ChatGPT connector UI doesn’t expose a custom auth header — same limitation as Claude.ai — you can embed an Organization MCP API Token in the server URL. Generate a token with a label likechatgpt, then create the connector with this URL instead of the bare endpoint:
Authorization header.
Verify
With the GetWhys connector enabled in the composer, ask the verify prompt: “Who am I in GetWhys?”Troubleshooting
Developer Mode toggle is missing — confirm your plan supports it, and that a ChatGPT workspace admin has allowed Developer Mode for your account. Connector creates but tools don’t appear — open the app in Settings → Plugins, click Refresh, and confirm the MCP URL is exactlyhttps://api.getwhys.io/mcp (or the query-string form if you’re using a token).
Tool calls fail with an auth error — re-authorize via OAuth, or generate a fresh Organization MCP API Token and update the connector URL if you used the query-string method.