Repository navigation
docs(mcp): ChatGPT connects with OAuth only (SB-001138) - #87
Merged
Merged
Conversation
…1138) ChatGPT developer-mode apps offer OAuth or no auth; there is no field for an API key or Authorization header. The guide said otherwise and BadgerBot repeated it to a customer whose OAuth sign-in was failing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ChatGPT MCP guide told users they could "select API-key auth and paste your key". ChatGPT developer-mode apps only offer OAuth (or no auth); there's no API-key or header field. BadgerBot repeated this to a customer in SB-001138 while their OAuth sign-in was failing (the OAuth failure itself was fixed in scrapebadger#2344 / SCR-314).
🤖 Generated with Claude Code