-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Clarify system key usage for MCP extension endpoints #127734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Updated the description of the system key requirement for MCP extension endpoints to include the 'code' querystring parameter.
@PaoloPia : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 43f8d22: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Updates documentation to clarify that the MCP extension system key can be provided via either HTTP header or querystring parameter. This clarifies the authentication options available for accessing MCP extension endpoints in Azure Functions.
- Clarified system key authentication methods for MCP extension endpoints
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Co-authored-by: Glenn Gailey <[email protected]>
Learn Build status updates of commit 36120f4: ✅ Validation status: passed
For more details, please refer to the build report. |
Updated the description of the system key requirement for MCP extension endpoints to include the 'code' querystring parameter.