Staff can now connect Claude with their own WordPress accounts, and posts are credited to them. Existing AI Agent connections keep working, and your saved settings are kept.<\/p>","1.8.0":"
Agents can no longer publish with featured images under 1,200 px wide (or your site's minimum) unless you allow it under Settings > Agent Publisher > Images.<\/p>","1.7.0":"
Adds image guidance and checks, a find-media tool for images you upload yourself, and one-step featured image replacement on live posts.<\/p>","1.6.1":"
Fixes Claude connectors failing with a server error on sites that run Limit Login Attempts Reloaded or similar plugins.<\/p>","1.6.0":"
Adds a one-click Claude Desktop extension for sites that can't use the connector. Includes the 1.5.0 security fixes.<\/p>","1.5.0":"
Security release: recommended for all sites, especially those in a Publish mode. Adds one-click setup and connection checks under Settings > Agent Publisher.<\/p>","1.4.0":"
create-draft-post is now create-post, which can also publish and set a featured image in one step. Restart Claude Desktop (or reconnect) after updating so it picks up the new tools.<\/p>","1.3.1":"
Fixes Claude Desktop not loading the tools that create and edit posts. Reconnect Claude (or restart Claude Desktop) after updating.<\/p>","1.3.0":"
The MCP Adapter is built in, and the new connection URL is \/wp-json\/acadium-agent-publisher\/mcp. Existing connections keep working.<\/p>","1.2.0":"
Adds optional OAuth so claude.ai and the Claude mobile apps can connect. Off until you enable it under Settings > Agent Publisher.<\/p>","1.1.0":"
Adds optional publishing. The default stays "Drafts only"; nothing changes until you pick another mode under Settings > Agent Publisher.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3721756,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3721756,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.0","1.6.0","1.6.1","1.7.0","1.8.0","1.9.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[251511,2353,229563,529,242115],"plugin_category":[],"plugin_contributors":[283715],"plugin_business_model":[],"class_list":["post-375607","plugin","type-plugin","status-publish","hentry","plugin_tags-abilities","plugin_tags-ai","plugin_tags-claude","plugin_tags-content","plugin_tags-mcp","plugin_contributors-anselbrandt","plugin_committers-anselbrandt"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/acadium-agent-publisher\/assets\/icon-128x128.png?rev=3721756","icon_2x":"https:\/\/ps.w.org\/acadium-agent-publisher\/assets\/icon-256x256.png?rev=3721756","generated":false},"screenshots":[],"raw_content":"\n
Acadium Agent Publisher lets an AI agent, such as Claude, write and publish blog posts for 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.<\/p>\n\n
Your staff connect Claude with their own WordPress accounts<\/strong>: the posts Claude writes are credited to and owned by the person who connected it. Claude works with limited permissions, never more than that person's own role: their own posts only, no settings, no other people's posts. Under Settings > Agent Publisher<\/strong> you decide how far Claude may go:<\/p>\n\n Each person's role still applies: a Contributor's Claude can only write drafts and submit them for review, in any mode.<\/p>\n\n Checks before an agent publishes:<\/p>\n\n Every agent action is listed under Recent agent activity on the settings page.<\/p>\n\n The Connect Claude<\/strong> section under Settings > Agent Publisher creates the AI Agent user, turns on connector sign-in (OAuth) and shows the connection URL. In Claude Desktop, claude.ai or the Claude mobile apps, add the site as a custom connector with that URL: no Application Password and no software on your computer.<\/p>\n\n Connection checks<\/strong> on the same page test HTTPS, permalinks, the connection URL, the Authorization header and connector sign-in from the server itself, and explain how to fix what fails (with a one-click .htaccess fix for the Authorization header on Apache). Sites that can't use the connector (for example, WordPress in a subfolder) can use the Claude Desktop extension instead: download it from the same page, create an Application Password there, and open the file. Claude Desktop installs it and runs it with its own Node.js, so there's nothing else to install and no configuration file to edit.<\/p>\n\n When you connect, an administrator logs in to WordPress and approves the connection, choosing which AI Agent user it acts as. The connection never gets the administrator's own permissions. Connected apps are listed on the settings page, and you can disconnect any of them.<\/p>\n\n Publishing can trigger things that unpublishing cannot undo, such as subscriber emails or social media posts from other plugins. Choose a stricter mode if posts should be reviewed by someone else before they go live.<\/p>\n\n They are available through the core Abilities REST API ( Filters:<\/p>\n\n Development happens on GitHub: https:\/\/github.com\/Acadium\/acadium-agent-publisher<\/p>\n\n\n Your site must use HTTPS. Sites the connector can't reach (for example WordPress in a subfolder) can use the Claude Desktop extension with an Application Password instead; see \"Can't use the connector?\" on the settings page.<\/p>\n\n\n Only if you choose \"Publish\" or \"Publish and edit live posts\" under Settings > Agent Publisher. By default it can only create drafts, and a person publishes them.<\/p><\/dd>\n No. The AI Agent role has no publishing capabilities, so the regular REST API refuses to publish or edit live posts for it in every mode. Only this plugin's abilities can do that, after checking your settings.<\/p><\/dd>\n Yes. Turn on \"Allow OAuth connections\" under Settings > Agent Publisher and add your site as a custom connector in claude.ai. Connectors added there are also available in the Claude mobile apps.<\/p><\/dd>\n No. The plugin includes the official MCP Adapter (https:\/\/github.com\/WordPress\/mcp-adapter) library. If the MCP Adapter plugin, or another plugin that includes it (such as WooCommerce), is also active, WordPress loads the newest copy once, so they do not conflict. The MCP Adapter's default endpoint, Only administrators. The connection always acts as the AI Agent user the administrator picks, never as the administrator. Disconnect it under Settings > Agent Publisher > Connected apps.<\/p><\/dd>\n No. It does not contact any server on its own. The upload ability downloads an image only when the agent supplies an image URL, and only from public https addresses. With OAuth on, apps such as claude.ai call your site's OAuth endpoints; your site does not call them.<\/p><\/dd>\n They are published by WordPress' scheduler (WP-Cron), like posts you schedule yourself. If your site disables WP-Cron, make sure a server cron job runs it.<\/p><\/dd>\n Revoke the agent's Application Password under Users > (agent) > Application Passwords, or delete the agent user. Deactivating the plugin removes the abilities.<\/p><\/dd>\n Check that \"Allow OAuth connections\" is on and that Your web server may be removing the Authorization header, which is common with Apache and CGI\/FastCGI. Add \n
\n
Connect Claude in a few clicks<\/h4>\n\n
Safety<\/h4>\n\n
\n
\n
Abilities<\/h4>\n\n
\n
agent-publisher\/get-capabilities<\/code> (read-only): what the site allows<\/li>\nagent-publisher\/list-terms<\/code> (read-only)<\/li>\nagent-publisher\/get-post<\/code> (read-only; any status, including published)<\/li>\nagent-publisher\/create-post<\/code> (as a draft, for review, or published in one step with its featured image)<\/li>\nagent-publisher\/update-draft-post<\/code><\/li>\nagent-publisher\/upload-media<\/code><\/li>\nagent-publisher\/find-media<\/code> (read-only: find images in the Media Library)<\/li>\nagent-publisher\/request-upload<\/code> (a one-time link where the user uploads their own image)<\/li>\nagent-publisher\/get-upload<\/code> (read-only: the image from an upload link)<\/li>\nagent-publisher\/submit-for-review<\/code><\/li>\nagent-publisher\/publish-post<\/code> (publish now or schedule)<\/li>\nagent-publisher\/unpublish-post<\/code><\/li>\nagent-publisher\/update-published-post<\/code> (including replacing the featured image)<\/li>\n<\/ul>\n\n\/wp-json\/wp-abilities\/v1\/<\/code>; read-only abilities use GET, the others POST) and, as one MCP tool each, at the plugin's MCP endpoint \/wp-json\/acadium-agent-publisher\/mcp<\/code> for clients such as claude.ai, Claude Desktop and Claude Code.<\/p>\n\nFor developers<\/h4>\n\n
\n
agent_publisher_post_types<\/code>: post types the post abilities work on (default: post<\/code>).<\/li>\nagent_publisher_post_meta<\/code>: custom field keys agents may read and write (default: none).<\/li>\nagent_publisher_upload_mimes<\/code>: accepted image types (default: JPEG, PNG, GIF, WebP).<\/li>\nagent_publisher_max_upload<\/code>: maximum upload size in bytes (default: 10 MB).<\/li>\n<\/ul>\n\n\n
\n
Can the agent publish posts?<\/h3><\/dt>\n
Can the agent bypass these settings through the REST API?<\/h3><\/dt>\n
Can I use it from the Claude mobile app?<\/h3><\/dt>\n
Do I need the MCP Adapter plugin?<\/h3><\/dt>\n
\/wp-json\/mcp\/mcp-adapter-default-server<\/code>, keeps working for connections made with version 1.2 or earlier.<\/p><\/dd>\nWho can approve an OAuth connection?<\/h3><\/dt>\n
Does this plugin connect to external services?<\/h3><\/dt>\n
Do scheduled posts need anything special?<\/h3><\/dt>\n
How do I revoke access?<\/h3><\/dt>\n
claude.ai cannot connect<\/h3><\/dt>\n
https:\/\/your-site\/.well-known\/oauth-authorization-server<\/code> shows a JSON document. OAuth discovery requires WordPress to be installed at the root of its domain, not in a subdirectory. A firewall or CDN must pass \/.well-known\/<\/code> and \/agent-publisher-oauth\/<\/code> requests to WordPress, and must forward the Authorization header.<\/p><\/dd>\nThe agent gets a 401 error although the password is correct<\/h3><\/dt>\n
SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1<\/code> to your .htaccess, and make sure security plugins allow Application Passwords and REST API access for logged-in users.<\/p><\/dd>\n\n<\/dl>\n\n\n1.9.0<\/h4>\n\n
\n
1.8.0<\/h4>\n\n
\n
1.7.0<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
create-post<\/code> replaces create-draft-post<\/code>. In one call it creates the post with categories, tags and a featured image (featured_image<\/code> uploads it), and can submit it for review or publish or schedule it when the site mode allows. An agent now needs one approval for a finished post instead of up to three.<\/li>\ncreate-post<\/code> creates nothing (including the uploaded image), so the agent can fix its input and try again.<\/li>\n1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
\/wp-json\/acadium-agent-publisher\/mcp<\/code> lists each ability as its own tool. The MCP Adapter default endpoint keeps working, including with OAuth.<\/li>\n1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n