> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ChatGPT

> Connect GetWhys to ChatGPT via Developer Mode connectors so OpenAI Chat can pull buyer research and messaging context.

Connect GetWhys to [ChatGPT](https://chatgpt.com) so drafts and research in OpenAI Chat can pull from your research interviews, personas, messaging frameworks, and brand voice.

ChatGPT supports remote MCP servers through **Developer Mode**. You'll need a ChatGPT plan that includes Developer Mode (Plus, Pro, Business, Enterprise, or Education on the web), and your workspace admin may need to allow Developer Mode for your account.

Complete the shared steps in [MCP Setup](/integrations/mcp-setup) first.

## Recommended: connect with GetWhys OAuth

### 1. Enable Developer Mode

1. In ChatGPT, open **Settings → Security and login**
2. Turn on **Developer mode**

If you don't see the toggle, ask your ChatGPT workspace admin to allow Developer Mode.

### 2. Create a developer-mode app / connector

1. Open **Settings → Plugins** (or go to [chatgpt.com/plugins](https://chatgpt.com/plugins))
2. Select the **+** button to create a new developer-mode app
3. Fill in:
   * **Name:** `GetWhys`
   * **Description:** e.g. *"Buyer validation: research interviews, personas, messaging frameworks, brand voice, and message testing."*
   * **MCP server URL:**

```text theme={null}
https://api.getwhys.io/mcp
```

4. Set authentication to **OAuth** (ChatGPT's preferred method for secured MCP servers)
5. Confirm you trust the application and click **Create**
6. Complete the GetWhys sign-in / authorize flow when prompted

You'll see GetWhys tools listed if the connection succeeds. In chat, enable the GetWhys app / Developer Mode tool when you want ChatGPT to call it.

## 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](/integrations/mcp-setup#generate-an-organization-mcp-api-token) with a label like `chatgpt`, then create the connector with this URL instead of the bare endpoint:

```text theme={null}
https://api.getwhys.io/mcp?access_token=<TOKEN>
```

Prefer OAuth when you can. Only use the [query-string token](/integrations/mcp-setup#authenticating-with-a-token-header-vs-query-string) if you need a shared org connection and your ChatGPT UI can't set an `Authorization` header.

## Verify

With the GetWhys connector enabled in the composer, ask the [verify prompt](/integrations/mcp-setup#verify-the-connection): "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 exactly `https://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.