Connecting ChatGPT Desktop
Configure ChatGPT's developer-mode connectors to work with Zuse Bifrost, by signing in or with a personal access token.
Requirements
- ChatGPT with developer mode connectors enabled (Plus, Pro, Team, Enterprise or Edu; on a workspace plan an admin may need to allow them).
- A Zuse Bifrost account. ChatGPT signs you in; a personal access token is only needed when you want a connection narrower than your own reach.
The server address is written as https://mcp.example.test below; use the one your administrator shares.
Add the connector
Open Settings → Connectors → Create (developer mode) and enter:
- Name:
Zuse Bifrost - MCP server URL:
https://mcp.example.test, exactly the address you were given, no trailing slash - Authentication: OAuth
Save. ChatGPT opens Zuse Bifrost in your browser: sign in if you are not already, read the consent screen and press Authorize. ChatGPT negotiates the MCP handshake and lists the tools in the connector panel.
Test
Open a fresh chat with the Zuse Bifrost connector enabled (toggle icon in the composer) and ask:
List my Zuse Bifrost projects.
The response includes which tool was invoked. If the call fails, inspect the error: every Zuse Bifrost MCP error carries a docs_url pointing back to this documentation.
Using a personal access token instead
Choose Authentication: No authentication on the connector, and add a custom header Authorization with the value Bearer zg_… from a token minted under Account Settings → API Tokens. ChatGPT then skips the sign-in and the connection carries only the abilities you ticked.
Scope tips
ChatGPT tends to invoke multiple tools per turn. For read-only exploratory chats, a personal access token with only view-any and view abilities keeps the assistant from writing anything. For workflows that register webhooks or tidy the Notifications Center, the OAuth connection is simpler; every tool that changes data is marked destructive, so ChatGPT asks before running it.
Troubleshooting
- Connector disabled: enable it in the composer toolbar for the current chat.
- Sign-in never completes: the URL must be exactly the server's address; finish the browser sign-in and try connecting again.
- Auth failed after a while: disconnect and reconnect the connector to sign in again; with a personal access token, re-mint it.
- A tool is refused with a personal access token: the token is missing the ability that specific tool enforces; the error envelope includes
required_abilityto make fixing it fast.
How is this guide?
Last updated on