Abilities API: Post Settings

[n7studios]

Summary

Registers get and update abilities (MCP tools) for the per-Post Kit settings (Form, Landing Page, Tag, Member Content / Restrict Content) stored in the _wp_convertkit_post_meta post meta, so an MCP client can fetch and update these settings for any Post, Page or Custom Post Type. Partial updates are supported; the Restrict Content cache stays in sync automatically via the existing updated_post_meta hook.

Ability	Description	Required input	Output
kit/post-settings-get	Returns the current Kit settings (form, landing_page, tag, restrict_content) for the given Post, Page or Custom Post Type.	{ post_id }	{ post_id, form, landing_page, tag, restrict_content }
kit/post-settings-update	Updates one or more Kit settings for the given Post, Page or Custom Post Type. Only the settings provided in the input are updated; other settings are preserved. Unknown keys are rejected.	{ post_id } plus a partial object of any subset of: form, landing_page, tag, restrict_content	same shape as kit/post-settings-get (post-save state)

Testing

• MCPPostSettingsGetTest: Tests that the MCP tool is registered, permissions are honored (edit_post capability required), defaults are returned when no post meta exists, stored values are returned when set, non-existent post IDs are rejected, and the tool works across post types (Post, Page).
• MCPPostSettingsUpdateTest: Tests that the MCP tool is registered, full and partial updates persist correctly, unknown keys and malformed form / restrict_content values are rejected, empty input is rejected, non-existent post IDs are rejected, the update → get round-trip returns the updated values, and setting or clearing restrict_content correctly populates or removes the Post from the Restrict Content cache.

Checklist

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

[n7studios]

This shouldn't have /mcp appended to it - not sure how this was added in an earlier PR.

[github-actions]

WordPress Playground

🚀 Your PR has been built and is ready for testing in WordPress Playground!

Click here to test your changes in WordPress Playground