Keep that dashboard or cockpit tab open and talk to your browser's AI\nagent.<\/li>\n<\/ol>\n\nRequirements: WordPress 6.0+, PHP 7.4+, and a browser or extension that\nimplements the experimental WebMCP API (document.modelContext<\/code>). Chrome 149+\noffers WebMCP through an origin trial or the\n chrome:\/\/flags\/#enable-webmcp-testing flag for local testing. WebMCP is in\nearly preview and its API may change.<\/p>\n\n\n\nCan the AI agent publish posts on its own?<\/h3><\/dt>\nNo. By design the agent can only create or update drafts and content in the\ndedicated review status. Published or scheduled content cannot be changed or\nmoved by an agent. Publishing is a separate, capability-protected action that\na human performs in the review queue.<\/p><\/dd>\n
Which AI agents work with this?<\/h3><\/dt>\nAny compatible browser agent or extension that uses the experimental WebMCP\nAPI (document.modelContext<\/code>). The Model Context Tool Inspector can list and\nmanually call tools for testing. Its natural-language prompts may be processed\nby an external AI provider, so review the extension\u2019s current terms before\nusing private content.<\/p><\/dd>\nDoes it send my content to external services?<\/h3><\/dt>\nThe plugin itself does not send your content to the plugin developer or another\nthird-party service. Tool calls reach your own WordPress REST API using your\nlogged-in session. However, the browser, AI agent, or extension you choose may\nsend prompts, page content, tool inputs, or tool results to its provider.\nReview that provider\u2019s terms and privacy policy before using private content.<\/p><\/dd>\n
Do I need an MCP server or API keys?<\/h3><\/dt>\nNo separate MCP server or plugin API key is required. The tools live on the\nWordPress admin page and the browser mediates between the agent and that page.\nThe browser agent itself may still require its own account or configuration.<\/p><\/dd>\n
Which browsers are supported?<\/h3><\/dt>\nChrome 149+ exposes experimental WebMCP through an origin trial or the\n chrome:\/\/flags\/#enable-webmcp-testing flag for local testing. Other browsers\nor extensions can work if they implement the current draft. WebMCP is an early\npreview, not a W3C Standard, and support may change. WordPress continues to\nwork normally when WebMCP is unavailable.<\/p><\/dd>\n
Does it work with Yoast SEO \/ Rank Math?<\/h3><\/dt>\nYes. SEO title, meta description and canonical URL written by the agent go\ndirectly into the active SEO plugin's fields. Without an SEO plugin, portable\ncustom fields are used.<\/p><\/dd>\n
What is the upload size limit for agent images?<\/h3><\/dt>\nBase64 image uploads accept PNG, JPEG, WebP and GIF up to\n min( wp_max_upload_size(), 10 MB ) of decoded data. The JSON request body is\nroughly 1.37\u00d7 the image size, so your host's post_max_size<\/code> must be at least\nthat; the error message names the exact limit when it is exceeded.<\/p><\/dd>\nDoes it work with WooCommerce or custom post types?<\/h3><\/dt>\nPosts and pages are supported out of the box. Additional post types and\ncapabilities can be added with the webmcp_cockpit_tools<\/code> filter \u2014 for\nexample WooCommerce product tools.<\/p><\/dd>\nWho can use the agent tools?<\/h3><\/dt>\nOnly logged-in users with the edit_posts<\/code> capability (authors, editors,\nadministrators). Media uploads additionally require upload_files<\/code>,\npublishing requires the publish capability. Guests and subscribers get\nnothing.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.11<\/h4>\n\n\n- Renames the plugin to Ostheimer Cockpit for WebMCP<\/strong> and aligns the plugin\nfolder, main file and text domain with
ostheimer-webmcp-cockpit<\/code>.<\/li>\n- Limits post-list results to posts the current user is allowed to edit, with\nregression coverage for separate author accounts.<\/li>\n
- Moves the plugin pages below WordPress Tools<\/strong> and removes the obsolete\nmanual translation loader and bundled runtime translation files.<\/li>\n
- Makes Plugin Check warnings fail the release check.<\/li>\n<\/ul>\n\n
1.0.10<\/h4>\n\n\n- Refines the WordPress dashboard box with a clearer action hierarchy, compact\nnative buttons and consistent spacing in narrow dashboard columns.<\/li>\n
- Keeps the copy action beside the prompt label and gives the review queue\nprimary emphasis above the two secondary links.<\/li>\n<\/ul>\n\n
1.0.9<\/h4>\n\n\n- Registers all WebMCP tools on the normal WordPress start dashboard (
\/wp-admin\/<\/code>)\nin addition to the dedicated Cockpit page.<\/li>\n- Adds a native, draggable dashboard box with live tool status, a copyable\nexample prompt, review count, and links to the Cockpit and activity log.<\/li>\n
- Adds server-side regression coverage for the dashboard widget and asset host.<\/li>\n<\/ul>\n\n
1.0.8<\/h4>\n\n\n- Adds a complete metadata-only audit trail for successful and failed WebMCP\ntool calls, including read tools such as
list_posts<\/code> and get_post<\/code>.<\/li>\n- Adds administrator filters for read\/write and tool\/workflow events, bulk\nselection, and nonce-protected deletion of selected, filtered or all log\nentries. Agents cannot delete the audit log.<\/li>\n
- Adds an automatic database migration for the activity type and tool-name\ncolumns when updating the plugin in place.<\/li>\n<\/ul>\n\n
1.0.7<\/h4>\n\n\n- Enforces the human review boundary: browser agents cannot update, publish or\nunpublish published or scheduled content; only the review queue can publish.<\/li>\n
- Completes the
create_post<\/code> and update_post<\/code> schemas for author, scheduling,\npassword, sticky, post format, page attributes and canonical URL fields.<\/li>\n- Keeps agent-facing source output in English and clarifies that the activity\nlog records agent write actions.<\/li>\n<\/ul>\n\n
1.0.6<\/h4>\n\n\n- Tool errors now return a machine-readable signal (
isError: true<\/code> plus a\nstable code<\/code>, following the MCP CallToolResult convention) instead of\nrelying on localized text prefixes. The readable, translatable message\nstays unchanged.<\/li>\n- Clarifies that WebMCP is experimental and distinguishes the plugin\u2019s own\ndata handling from external processing by a chosen browser or AI agent.<\/li>\n<\/ul>\n\n
1.0.5<\/h4>\n\n\n- Sharper agent-facing tool descriptions: http(s)-only URLs for\n upload_media, formats\/size limit\/filename handling for\n upload_media_base64, precedence and failure behaviour for\n featured_image_url\/
featured_media_id<\/code>, and the warning behaviour of\n create_post when a featured image fails.<\/li>\n- Regression suite (
tests\/<\/code>) and documentation for server-side edge cases.<\/li>\n<\/ul>\n\n1.0.4<\/h4>\n\n\n- i18n: the plugin source is now fully English and translation-ready.\nA German (de_DE) translation ships with the plugin.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Fix: a failed featured-image import from
featured_image_url<\/code> (e.g. a URL\nthat returns no image) no longer reports success and no longer touches an\nexisting featured image; imported attachments are verified as real images\nfrom the downloaded bytes, failed imports are cleaned up.<\/li>\n- Fix: error messages now name the originally submitted value for invalid\nmedia IDs (e.g.
-5<\/code>) and distinguish URL format errors from network\/DNS\nerrors.<\/li>\n<\/ul>\n\n1.0.2<\/h4>\n\n\n- Fix: invalid
featured_media_id<\/code> values now return a clear error instead of\na silent success; attachments are validated for existence and image type.<\/li>\n- Fix: rejected media uploads (wrong type, broken Base64, size limit) are now\nrecorded in the activity log as
media_rejected<\/code> entries.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n\n- New:
upload_media_base64<\/code> tool \u2014 agents can upload self-generated images\n(PNG, JPEG, WebP, GIF) directly into the media library without a public URL.\nReal MIME type is verified from the decoded bytes; size capped at 10 MB.<\/li>\n- New:
featured_media_id<\/code> parameter for create_post<\/code>\/update_post<\/code> \u2014 assign\na featured image from an existing media ID (takes precedence over\n featured_image_url).<\/li>\n- Tool errors now return readable messages to the agent.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release: 10 agent tools for creating, updating and reviewing posts,\nfull post field coverage, featured images from URL, taxonomy assignment by\nname, SEO plugin integration (Yoast SEO, Rank Math), review workflow with\nhuman approval, activity log, rate limiting and a PHP API for custom tools.<\/li>\n<\/ul>","raw_excerpt":"Let browser-based AI agents write, edit and manage WordPress posts \u2014 with a human review step before anything is published.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361226","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361226"}],"author":[{"embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/helpstring"}],"wp:attachment":[{"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361226"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361226"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361226"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361226"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361226"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/mai.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361226"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}