by
Andreas Ostheimer
0 (0 reviews)
Ostheimer Cockpit for WebMCP
Let browser-based AI agents write, edit and manage WordPress posts — with a human review step before anything is published.
Ostheimer Cockpit for WebMCP ranks #71,327 among WordPress.org plugins with 0+ active installations, and was last updated Oct 4, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.0.14
Current Version v1.0.14
Updated 1 month ago
Last Update on 04 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Rank
#71,327
—
No change
Active Installs
0+
-100%
KW Avg Position
29
1 worse
Downloads
353
+3 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
43,759
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#71,327
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.14
- Last Updated
- Oct 04, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Andreas Ostheimer
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Ostheimer Cockpit for WebMCP
No. By design the agent can only create or update drafts and content in the dedicated review status. Published or scheduled content cannot be changed or moved by an agent. Publishing is a separate, capability-protected action that a human performs in the review queue.
Any compatible browser agent or extension that uses the experimental WebMCP API (document.modelContext). The Model Context Tool Inspector can list and manually call tools for testing. Its natural-language prompts may be processed by an external AI provider, so review the extension’s current terms before using private content.
It can triage them. list_comments shows pending, approved or spam comments, and moderate_comment approves, unapproves or marks a single one as spam. Both require the moderate_comments capability, so a subscriber or author account cannot touch the queue. Comment listings never include the author's email address or IP address. The agent does not need either to sort spam from real comments, and both would leave your site with the response.
Yes, but the same review boundary applies as everywhere else: list_revisions and compare_revisions need the edit_post capability on the post the revision belongs to, and restore_revision can only act where update_post could also write — drafts and content in the pending review status. A published or scheduled post's revisions can be listed and compared, but not restored by an agent. Restoring is itself reversible: WordPress saves the pre-restore state as a new revision first, exactly as it does when you restore a revision by hand in wp-admin.
The plugin itself does not send your content to the plugin developer or another third-party service. Tool calls reach your own WordPress REST API using your logged-in session. However, the browser, AI agent, or extension you choose may send prompts, page content, tool inputs, or tool results to its provider. Review that provider’s terms and privacy policy before using private content.
No separate MCP server or plugin API key is required. The tools live on the WordPress admin page and the browser mediates between the agent and that page. The browser agent itself may still require its own account or configuration.
Chrome 149+ exposes experimental WebMCP through an origin trial or the chrome://flags/#enable-webmcp-testing flag for local testing. Other browsers or extensions can work if they implement the current draft. WebMCP is an early preview, not a W3C Standard, and support may change. WordPress continues to work normally when WebMCP is unavailable.
Yes. SEO title, meta description and canonical URL written by the agent go directly into the active SEO plugin's fields. Without an SEO plugin, portable custom fields are used.
Base64 image uploads accept PNG, JPEG, WebP and GIF up to min( wp_max_upload_size(), 10 MB ) of decoded data. The JSON request body is roughly 1.37× the image size, so your host's post_max_size must be at least that; the error message names the exact limit when it is exceeded.
Posts and pages are supported out of the box. On the plugin's settings page (Tools → Settings) you choose which of the two agents may work with; content of a type you switch off stays out of reach, drafts, revisions and comments included. Additional post types and capabilities can be added with the webmcp_cockpit_tools filter — for example WooCommerce product tools.