Skip to content

docs(plugin-mcp): clarify Bearer-only auth on /api/mcp endpoint #16602

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.

Sign up for GitHub

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

Closed
algojogacor wants to merge 1 commit into from
Closed

docs(plugin-mcp): clarify Bearer-only auth on /api/mcp endpoint #16602

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion docs/plugins/mcp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,17 @@ toggle the individual capabilities on for each collection, global, tool, prompt,
resource you want that key to be able to use.

All MCP requests must include a valid API key as a Bearer token — requests without
one are rejected immediately. Here is a complete example of an MCP `tools/list` request
one are rejected immediately.

<Banner type="info">
Unlike other Payload API-key-based endpoints that accept the
`<collection-slug> API-Key <key>` convention, the MCP endpoint
**only** supports `Authorization: Bearer <key>`. Using
`payload-mcp-api-keys API-Key <key>` or any other auth scheme will
be rejected.
</Banner>

Here is a complete example of an MCP `tools/list` request
showing the correct headers:

```bash
Expand Down
Loading