Acadium AI Site Editor

Acadium AI Site Editor (formerly Acadium Agent Publisher) lets an AI assistant such as Claude write, edit and publish content on your site through the WordPress Abilities API and the Model Context Protocol (MCP). The official MCP Adapter library is built in, so there is nothing else to install.

Your staff connect Claude with their own WordPress accounts. What Claude creates is credited to the person who connected it, and Claude can do only what that person’s WordPress role allows:

• Posts and pages: create, edit, publish, schedule, unpublish, move to the Trash and restore earlier versions. Editing someone else’s content keeps its original author.

• Exact edits: change a headline, sentence or link without resending the whole page, so the rest of the page stays untouched.

• Synced patterns: edit shared blocks such as a site header, footer or banner (Editors and Administrators).

• Navigation menus: add, rename, move and remove menu links, with one-step undo (Administrators).

• Categories and tags: create, rename, merge and delete (Editors and Administrators).

• Images: upload, use as featured images, and edit alt text, captions and titles.

• Redirects: add and remove redirects, for example when a page’s address changes (Administrators). Uses the Redirection plugin when it is active.

Claude can never permanently delete posts, pages or images, or change site settings, users, plugins or themes.

Under Settings > AI Site Editor you decide how far Claude may go on the whole site:

• Drafts only: Claude creates and edits drafts, and a person publishes them.

• Submit for review: Claude can also move drafts to “Pending review” for an editor.

• Publish: Claude can also publish or schedule posts, after the checks you set, and unpublish them again.

• Publish and edit live posts (default): Claude can also change live content, menus, categories and redirects.

Each person’s role still applies in every mode: a Contributor’s Claude can only write drafts and submit them for review.

Optional checks before Claude publishes: a featured image with alt text and a minimum width, allowed categories, and a daily limit. Every action Claude takes is listed under Recent activity on the settings page.

Connect Claude in a few clicks

Copy the connection URL from Settings > AI Site Editor and share it with your staff. ai or the Claude mobile apps) as a custom connector, logs in with their own WordPress account and clicks Allow. No Application Password and no software on their computer.

Connection checks on the same page test HTTPS, permalinks, the connection URL, the Authorization header and connector sign-in, and explain how to fix what fails. Sites that can’t use the connector (for example, WordPress in a subfolder) can use the Claude Desktop extension with an Application Password instead.

Safety

• Your role, nothing more. A connection can only do what the person’s own role allows for content, and never touches settings, users, plugins or themes.

• Nothing is lost silently. WordPress keeps revisions of posts, pages and patterns; menus are snapshotted before every change; a change that would strip markup the person’s role can’t save is refused instead.

• Page builders are respected. Claude is told when a page builder (Beaver Builder, Elementor, Divi, WPBakery) draws a page, and content edits that wouldn’t show are refused.

• Uploads are checked. The real file type must be JPEG, PNG, GIF or WebP, the size is limited, and URL uploads only fetch from public https addresses.

• Secure sign-in. OAuth 2.1 with PKCE; access tokens expire after an hour, refresh tokens are single-use and stored only as hashes, and tokens work only for the MCP and Abilities API routes. Administrators can disconnect any connection.

Publishing can trigger things that unpublishing cannot undo, such as subscriber emails or social media posts from other plugins. Choose a stricter mode if content should be reviewed before it goes live.

Abilities

Content:

• agent-publisher/get-capabilities (read-only): what the site and the person’s role allow

• agent-publisher/find-posts, get-post (read-only): posts, pages and synced patterns

• agent-publisher/create-post, update-draft-post, update-published-post

• agent-publisher/submit-for-review, publish-post (now or scheduled), unpublish-post

• agent-publisher/trash-post, restore-revision

Site:

• agent-publisher/list-menus, create-menu, update-menu, restore-menu

• agent-publisher/list-terms, create-term, update-term, delete-term

• agent-publisher/list-redirects, create-redirect, delete-redirect

Images:

• agent-publisher/upload-media, find-media, update-media

• agent-publisher/request-upload, get-upload: a one-time link where the user uploads their own image

They are available through the core Abilities REST API ( /wp-json/wp-abilities/v1/; read-only abilities use GET, the others POST) and, as one MCP tool each, at /wp-json/acadium-agent-publisher/mcp. Ability and endpoint names are unchanged from Acadium Agent Publisher, so existing connections keep working.

For developers

Filters:

• agent_publisher_post_types: post types the content abilities work on (default: post, page, wp_block ).

• agent_publisher_can_connect: who may connect Claude (default: anyone who can write posts).

• agent_publisher_post_meta: custom field keys agents may read and write (default: none).

• agent_publisher_upload_mimes: accepted image types (default: JPEG, PNG, GIF, WebP).

• agent_publisher_max_upload: maximum upload size in bytes (default: 10 MB).

com/Acadium/acadium-agent-publisher