Connect ChatGPT
Add this workspace to ChatGPT as a developer-mode MCP connector.
Get the connection URL first
Open Settings → MCP in the helpdesk and copy the connection URL. It is that
deployment's own address, and a deployment with MCP switched off shows no URL
because there is nothing to connect to. Every <MCP-HOST-PLACEHOLDER> below is
that value.
The steps have been written from ChatGPT's current documentation and from this server's transport and authentication configuration, both of which are readable in source. They have not been proved by driving a ChatGPT account against a public deployment of this product.
What you are connecting to
| URL | https://<MCP-HOST-PLACEHOLDER>/mcp |
| Transport | Streamable HTTP |
| Credential | An OAuth 2.0 bearer token, in the Authorization header |
| Scope required | The one named in scopes_supported on the discovery document |
ChatGPT supports SSE and streaming HTTP as MCP transports, and OAuth as an authentication type, which is what this endpoint serves.
Source: services/runtime/src/runtime/mcp/asgi.py for the path, methods and
authentication chain, services/runtime/src/runtime/mcp/well_known.py for the
discovery document.
The procedure
1. Turn on developer mode
On a personal account: Settings → Security and login, then turn on Developer mode.
On a Business or Enterprise workspace an admin turns it on for the workspace instead, under Workspace settings → Permissions & roles → Connected data.
2. Create the connector
Go to ChatGPT plugins, press +, and create a developer-mode app for a remote MCP server.
3. Point it at this workspace
Paste the connection URL as the MCP server URL, choose OAuth as the authentication type, and save.
4. Sign in
ChatGPT sends you to the helpdesk's sign-in page. You sign in as yourself; there is no key to paste and no shared credential. Everything the connector then does is scoped to that workspace and to your role.
5. Confirm with a tool call
Ask ChatGPT to list your open tickets. That drives list_tickets, which needs
only the viewer role and no arguments at all.
If you belong to more than one workspace, the first call is refused and asks you
to name one. Ask again naming the workspace, which the client passes as
workspace_id.
Two things worth knowing
Deep research and company knowledge are a different mode. That mode expects
a server to publish two read-only tools named search and fetch. This server
publishes neither of those names, so use the developer-mode connector rather
than expecting it to appear as a research source.
Availability follows the plan. Developer mode is available to Pro, Plus, Business, Enterprise and Education accounts, on the web.
If a step fails
The failures are the same ones every client hits, and they look different from each other. Troubleshooting lists them with what to do about each.