Hi @meteorlxy,
Thanks for the suggestion! I’ve added a type filter to the wp_get_comments MCP tool, so agents can now read WordPress 6.9 editor Notes with type: “note”. It handles the note-specific detail too: notes track their state via comment status (open vs resolved), so when reading notes it returns all of them by default instead of only resolved ones, and the response now includes comment_type so you can tell notes apart. Resolving/unresolving a note also already works through wp_update_comment (it’s just the comment status).
This covers reading and triaging notes, which I’d guess is the main use case. Full note authoring (wp_create_note) is more involved, because a real note also has to be anchored to a specific block via the block’s metadata, so a plain comment insert isn’t enough. Before I build that: is your use case mostly reading/triaging notes, or do you also need to create them from an agent? That’ll help me decide whether the dedicated create tool is worth adding.
This’ll be in an upcoming release. Thanks again!
Best,
Jordy
Hi @tigroumeow ,
Thanks for the quick response!
We’ll need to create / read / delete / update notes from an agent. Considering that WordPress 6.9 now supports notes natively, our team is looking into migrating the entire workflow over to the WordPress + agents. This involves reviewing the articles and adding notes, similar to our PR review process.
Even putting aside our specific use case, I believe we should provide full notes management capabilities from our plugin perspective.
Thanks a lot!