fix(plugin-mcp): accept both Bearer and API-Key authorization patterns#16577
Open
algojogacor wants to merge 1 commit into
Open
fix(plugin-mcp): accept both Bearer and API-Key authorization patterns#16577algojogacor wants to merge 1 commit into
algojogacor wants to merge 1 commit into
Conversation
The MCP plugin endpoint /api/mcp currently only accepts Authorization: Bearer <KEY>. This is inconsistent with Payload's standard API-Key pattern. This change updates the authorization check to accept both: - Authorization: Bearer <KEY> - Authorization: API-Key <KEY>
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.
Description
The MCP plugin endpoint
/api/mcpcurrently only acceptsAuthorization: Bearer <KEY>header. This is inconsistent with Payload's standard API-Key authorization pattern which uses<collection-slug> API-Key <KEY>.This PR updates the authorization check in
packages/plugin-mcp/src/endpoints/mcp.tsto accept both patterns:Authorization: Bearer <KEY>(existing behavior)Authorization: API-Key <KEY>(new — matches Payload's standard pattern)Related Issue
Fixes #16572
Changes
getDefaultMcpAccessSettingsto check for bothBearerandAPI-Keyprefixes in the Authorization header