Skip to main content
Connect ChatGPT to GetWhys through a custom plugin. The connection uses organization-level access, so it isn’t tied to one GetWhys user.

​
Before you start

​
Add GetWhys to ChatGPT

1

Enable developer mode

In ChatGPT, open Settings → Security and login and turn on Developer mode.
ChatGPT Security and login settings with the Developer mode toggle turned on

Turn on Developer mode in Security and login settings

2

Open the plugin form

Go to chatgpt.com/plugins and click the + button.
ChatGPT Plugins page with the plus button beside the plugin search field

Click the plus button on the Plugins page

If you don’t see the + button, return to Settings → Security and login and make sure Developer mode is on.
3

Enter the GetWhys details

Complete the form with these values:Check I understand and want to continue, then click Advanced OAuth settings.
ChatGPT New Plugin form filled out for GetWhys with OAuth selected and Advanced OAuth settings visible

Enter the GetWhys server details and open Advanced OAuth settings

4

Configure the OAuth client

In Advanced OAuth settings:
  1. Set Registration method to User-Defined OAuth Client.
  2. Enter the OAuth Client ID and OAuth Client Secret from GetWhys.
  3. Set Token endpoint auth method to client_secret_basic.
ChatGPT OAuth advanced settings with User-Defined OAuth Client and client_secret_basic selected

Use the OAuth client credentials generated in GetWhys

5

Create the plugin

Click OK to save the OAuth settings, then click Create.

​
Verify the connection

Enable GetWhys in the ChatGPT composer, then ask: “Who am I in GetWhys?” If ChatGPT returns your GetWhys organization, you’re connected.

​
Troubleshooting

Developer Mode is unavailable — confirm that your plan supports it and that your workspace admin has enabled it. GetWhys tools don’t appear — open the plugin settings, click Refresh, and confirm the server URL is exactly https://api.getwhys.io/mcp/org. A tool call returns an authentication error — confirm the client ID and secret, and make sure Token endpoint auth method is set to client_secret_basic.