An agent can create, read, update, schedule, duplicate and delete blog posts, manage tags, categories and comments, upload or delete media, set a featured image, and pull basic site info, stats and revision history, through 27 abilities that map closely to core WordPress content operations.
View Postnova for MCP on WordPress.org
Needs WordPress 6.9 or later for the Abilities API (the plugin itself supports 6.8+) and the plugin active, with the individual ability not disabled in Postnova's settings (none are disabled by default). Read abilities need edit_posts, while category, tag, plugin-facing and media-deletion abilities need manage_categories, upload_files or delete_posts depending on the action.
All 27 ability ids and their capability checks are read directly from the plugin's registration calls; none of them set a readonly/destructive/idempotent annotation, which per the Bridge's fail-safe rule makes all 27 destructive, not just the ones that actually change data.
Grouped by what each one can change. Every one starts off until you enable it.
Create a new WordPress blog post.
Update title, content, status, excerpt, tags, or categories of an existing post.
Retrieve a list of blog posts with optional filters.
Retrieve full content and metadata of a single post by ID.
Retrieve all post tags with their IDs, names, slugs, and post counts.
Retrieve all post categories with their IDs, names, slugs, and post counts.
Schedule a post to be published automatically at a future date and time.
Create a new post tag.
Duplicate an existing post as a new draft, preserving content, tags, and categories.
Retrieve comments, optionally filtered by post or status.
Create a new post category.
Approve, hold, spam, or trash a comment.
Upload a media file to the WordPress Media Library by fetching it from a public URL.
Set the featured image of a post using a media attachment ID.
Edit the name, slug, or description of an existing tag.
Edit the name, slug, description, or parent of an existing category.
Permanently delete a tag; posts using it have it removed.
Permanently delete a category; posts are reassigned to the default category.
Post a reply to an existing comment as the current user.
Browse the WordPress Media Library with optional search and type filters.
Permanently delete a media attachment from the library.
Retrieve site name, URL, timezone, language, and WordPress version.
Get an overview of post, comment, and media counts by status.
List recent revisions for a post.
Retrieve the content and metadata of a post revision.
Restore a post to a previous revision.
Move a post to trash, or permanently delete it if already trashed.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Postnova for MCP registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Postnova for MCP starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. It registers 27 blog-management abilities directly in the core Abilities API with no annotations at all, so the Bridge's fail-safe rule treats every one of them, including plain list and get calls, as destructive.
each of the 27 abilities can be individually turned off via a settings-page checkbox stored in postnova_disabled_abilities; the option defaults to an empty list, so all 27 are enabled out of the box.
Needs WordPress 6.9 or later for the Abilities API (the plugin itself supports 6.8+) and the plugin active, with the individual ability not disabled in Postnova's settings (none are disabled by default). Read abilities need edit_posts, while category, tag, plugin-facing and media-deletion abilities need manage_categories, upload_files or delete_posts depending on the action.
An agent can read OttoKit's SaaS connection status, access-control settings, system health (cron jobs, database table, webhook log counts), configured automation triggers, which supported integrations are active, and paginated webhook execution logs.
Once an operator turns on the relevant feature toggles, an agent can read a site's exposed settings, users, and post content and terms, and can ask the plugin's AI experiments to draft or suggest excerpts, titles, slugs, meta descriptions, editorial notes and updates, summaries, translations, classifications, type-ahead text, image alt text, generated images, and comment moderation or reply suggestions, though running the content-generation ones also needs an AI connector configured.
An AI agent can create a new AutomatorWP automation, add triggers or actions to an existing one, and run or execute an automation's actions immediately, using AutomatorWP's own no-code automation builder.
Verified from Postnova for MCP's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, afatyo or Postnova for MCP. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.