feat: nextjs-mcp-js quickstart content-type update, new CIMD tenant setting mention#78
Open
feat: nextjs-mcp-js quickstart content-type update, new CIMD tenant setting mention#78
Conversation
priley86
changed the title
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
1 participant
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.
This change applies a few small improvements for the upcoming Auth0 MCP CIMD rollout (further SDK / Quickstart improvements will come in future efforts/PRs):
client_id_metadata_document_supportedtenant setting (will soon be supported after the upcoming Manual CIMD rollout) and being added to the Auth0 CLI: feat: add client_id_metadata_document_supported tenant settings support auth0/auth0-cli#1491content-type: application/jsonheaders with the/.well-known/*endpoints (e.g. ./.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource). This bug was encountered while testing this quickstart alongside an OpenAI AppSDK integration, and has been verified to work. (example: https://demo-trade-pro-agent.vercel.app/.well-known/oauth-authorization-server for running mcp server sample)