One-click OAuth: connect Claude Desktop or ChatGPT with a single URL
August 9, 2026 MCPOAuthSetup

The GameFoundry MCP endpoint now speaks OAuth 2.1 with dynamic client registration. Paste the endpoint URL into Claude Desktop or ChatGPT's custom connector dialog, click Allow, and you're publishing.
The first version of GameFoundry MCP used personal-access bearer tokens: mint one from /dashboard/api-tokens, drop it into a config file. That still works, and it is the right path for terminal-native clients like Claude Code and Cursor. But Claude Desktop and ChatGPT ship with a native custom-connector UI that expects OAuth, and we heard from folks that the token flow was friction.
Now you paste the endpoint URL, click Connect, sign in to GameFoundry if you are not already, and click Allow. That's it. No token to copy, no config file to edit.
What's happening under the hood
- OAuth 2.1 with PKCE (the modern, safer variant of the flow)
- Dynamic client registration (RFC 7591) so we do not have to manually approve each MCP client
- Discovery via /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource (RFC 9728)
- Revoke any active connection from /dashboard/connected-clients
The two paths coexist: OAuth for browser-based clients, personal-access tokens for CLI clients. Pick whichever fits.
Try it now
Connect your MCP client