Payload MCP Plugin — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Payload plugin adding MCP capabilities to a CMS installation: Do plugin tool scopes follow Payload access control as the CMS and plugin versions change?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Exposing selected Payload CMS collections/globals as governed MCP tools

What we know

Official Payload plugin that adds MCP capabilities with per-collection/global operation controls and custom prompts, tools and resources.

Maintenance / activity evidence

@payloadcms/plugin-mcp 3.90.2 published 2026-09-23T13:55:27.929Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Intersection of Payload user access control and MCP collection/global capability config. Writes: Create/update/delete documents when enabled; Update globals when enabled.
Payload MCP API key.
Sensitive access: CMS content, Potential PII/private fields

Read-only configurations can be narrow, but enabling create/update/delete gives the model direct CMS mutation authority.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 412.9k package downloads / 30 days

Downloads observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Do plugin tool scopes follow Payload access control as the CMS and plugin versions change?

The bounded review of the publisher's documented Payload plugin adding MCP capabilities to a CMS installation and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Read-only configurations can be narrow, but enabling create/update/delete gives the model direct CMS mutation authority.
Intersection of Payload user access control and MCP collection/global capability config.
Payload MCP API key.
CMS records returned to MCP client; `overrideResponse` can strip sensitive fields.
Reviewed write actions: Create/update/delete documents when enabled; Update globals when enabled
Sensitive access: CMS content, Potential PII/private fields
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Every extra enabled operation increases unintended-action risk.
Payload access controls, API-key permissions and MCP capability controls all apply together.

Original activity observations

@payloadcms/plugin-mcp 3.90.2 published 2026-09-23T13:55:27.929Z

Technical identity

npm/@payloadcms/plugin-mcp

Exact implementation source: https://www.npmjs.com/package/@payloadcms/plugin-mcp ↗
Reviewed resource type: SDK
Package identity: @payloadcms/plugin-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

Package registry ↗
@payloadcms/plugin-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Repository document ↗
payloadcms/payload
Recorded repository material and project history.
Evidence source ↗
payloadcms.com/docs/plugins/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not a generic MCP Server; installation means product/developer integration, not a client registration.
Targeted 2026-10-13 re-research: Payload CMS plugin requires compatible CMS application/configuration; npm install is not an independent MCP process.
Payload CMS plugin requires compatible CMS application/configuration; npm install is not an independent MCP process.
Payload CMS plugin SDK. npm README lacks usable setup instructions; consult package-specific integration guide, do not invent launcher.
Avoid inventing launch command.
Do not claim a standalone MCP tool handshake.
Never paste credentials into chat.
Checked against publisher README or official docs; not executed. A library install is not MCP host registration.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.

Install / integrate application plugin
Publisher instructions
Developer library/integration. Install in an application; not a plug-and-play MCP Server. Review publisher README. Not a standalone local MCP server; application integration required.
publisher documented install or connection · Publisher instructions
pnpm add @payloadcms/plugin-mcp
Configure / authenticate
MCP100 setup guide
In Payload buildConfig.plugins add mcpPlugin with explicit allowed collections and operations, create scoped MCP access credentials in Payload, deploy, then connect the application /api/mcp endpoint. Merely installing package does not expose a standalone server.
Check connection
Suggested check
Official Payload: after adding mcpPlugin and authorizing a restricted API key, MCP Inspector or read-only POST tools/list to http://localhost:3000/api/mcp with Bearer key; do not test create/update/delete. SDK/plugin validation means app import/initialization or feature availability, not an MCP client tools/list test unless the consuming app actually exposes a server.
Remove / uninstall / revoke
MCP100 setup guide
Disable `mcpPlugin` inside Payload buildConfig.plugins and remove the project dependency with `pnpm remove @payloadcms/plugin-mcp`; redeploy and unregister the hosted /api/mcp connection from clients. Retain Payload database content.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Payload admin MCP -> API Keys can disable/limit specific key capabilities. For complete token revocation, disable/delete the API-key record in the app under your administration; exact deletion workflow not demonstrated.
Package / application cleanup · matching installation environment · MCP100 composed guide
pnpm remove @payloadcms/plugin-mcp

Official Documentation & Sources

What it does

Official Payload plugin that adds MCP capabilities with per-collection/global operation controls and custom prompts, tools and resources.

Capability: Data & Databases
Resource type: SDK
Industry: Media & Marketing, Software & Technology
Best fit: Exposing selected Payload CMS collections/globals as governed MCP tools

Representative uses

Expose collection find/create/update/delete
Expose global find/update
Add custom MCP tools/prompts/resources
Connect clients with API keys

Limitations

Every extra enabled operation increases unintended-action risk.
Payload access controls, API-key permissions and MCP capability controls all apply together.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Payload MCP API key.
Permissions: Intersection of Payload user access control and MCP collection/global capability config.
Data handling: CMS records returned to MCP client; `overrideResponse` can strip sensitive fields.
Cost: unknown
Risk and cautions: Read-only configurations can be narrow, but enabling create/update/delete gives the model direct CMS mutation authority.

Access scope and cautions

Write actions: Create/update/delete documents when enabled Update globals when enabled
Sensitive access: CMS content Potential PII/private fields
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Expose collection find/create/update/delete; Expose global find/update; Add custom MCP tools/prompts/resources; Connect clients with API keys.

What setup and authentication are documented?

Recorded installation/entrypoint step: pnpm add @payloadcms/plugin-mcp. Recorded transport: streamable_http. Prerequisites: Payload application. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Payload MCP API key associated with a Payload user.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete documents when enabled; Update globals when enabled. Recorded permission boundary: Intersection of Payload user access control and MCP collection/global capability config.

What data-handling boundary should I consider?

CMS records returned to MCP client; `overrideResponse` can strip sensitive fields. Recorded sensitive-access context: CMS content; Potential PII/private fields.

What limitations and risks should I check before use?

Read-only configurations can be narrow, but enabling create/update/delete gives the model direct CMS mutation authority. Every extra enabled operation increases unintended-action risk. Payload access controls, API-key permissions and MCP capability controls all apply together. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Payload is listed as First-party MCP in MCP100’s current evidence.