feat(plugin-mcp): add draft parameter support to MCP find resource tool #14924
Conversation
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
# Conflicts: # test/plugin-mcp/int.spec.ts
kendelljoseph
approved these changes
Jan 9, 2026
Contributor
|
🚀 This is included in version v3.71.0 |
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.
What?
Add
draftparameter support to the MCP plugin's find toolWhy?
MCP clients currently have no way to query draft/unpublished documents. When a collection has drafts enabled, agents need the ability to retrieve draft versions of documents for preview, editing workflows, or content management tasks.
How?
draftboolean parameter to thefindResourcesschema inschemas.tsfind.tsto accept and pass thedraftparameter to bothpayload.find()andpayload.findByID()calls