Skip to content

v0.3.3 — disabled option + MCP-disabled boot fix

Choose a tag to compare

View all tags
@ricbwood ricbwood released this 06 Jun 11:01
· 21 commits to main since this release
v0.3.3
a148f0d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Adds a disabled option and stops a disabled MCP plugin from crashing boot

disabled?: boolean

Turn the OAuth layer off without uninstalling: no endpoints, no token-validation wiring, mcpPluginOptions left untouched (the MCP server keeps working with API keys only). The OAuth collections stay registered — they're relationally isolated (text FKs, lockDocuments: false), so this keeps the DB schema consistent for migrations, matching @payloadcms/plugin-mcp and the official plugin template.

Fix: disabled MCP plugin no longer crashes boot (#55)

@payloadcms/plugin-mcp registers no /mcp endpoint when its own disabled is set, which made our detectMcpEndpoints() throw PLUGIN_ORDER and 500 the app. We now read the shared mcpPluginOptions.disabled and treat it as our disabled state (no throw, no overrideAuth mutation, collections kept). We still throw PLUGIN_ORDER when MCP is enabled but no /mcp endpoint exists (genuine misconfig).

Both reduce to one no-op condition: options.disabled || mcpPluginOptions.disabled.

Closes #49, #55. Patch release — purely additive.

Full diff: #56

Assets 2
Loading