#17 Fix, OAuth registration support to any MCP endpoint #21
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.
Problem
Chatgpt developer mode was failing to register custom OAuth connectors with the MCP endpoint https://api.supermemory.ai/mcp, returning a validation error:
This was simply a ChatGPT-specific compatibility issue where the response was being parsed as a string instead of a JSON object.
Solution
Fixes #17
This PR implements a complete OAuth client registration flow with proper CORS handling:
Proposed solutions works with any MCP client supporting OAuth 2.0 and supports proper JSON serialization with
Content-Type: application/jsonheaders