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.
OpenStation abilities, governed through the Bridge
An agent can read posts, pages, media and comments, search the site and the WordPress.org plugin directory, and inspect the PHP error log and the source around its lines. It can also update post content and media metadata, and create draft posts.
- Abilities
- 1916 read3 destructive
- Active installs
- 1K+
- Rating
- 100% (23 ratings)
- Version checked
- 1.1.19
- Requires
- WP 6.0+, PHP 7.4+
- Last updated
- 2026-11-06
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View OpenStation on WordPress.org
What has to be true first
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.0), plus PHP 7.4 or later and the plugin active. Of the 19 abilities, 6 check 'read'; 2 check 'upload_files'; 2 check 'edit_post'; 1 check 'read_post'; 1 check 'edit_pages'; 1 check 'delete_others_posts'; 1 check 'manage_options'; 1 check 'moderate_comments'; for 4 the permission check runs through a helper or filter, so no single capability is listed here.
A note on the count below
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
The 19 OpenStation abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Read 16
- Read
Get post by id
Return a post, title, content, excerpt, status, author, dates, by its numeric id.
contentis the RAW stored content exactly as saved, with block delimiter comments (<!-- wp:… -->) intact; it is never rendered output, so it is safe to edit and write back. Honours the caller's read capability. - Read
Get media details
Return details for a media library item (attachment) by numeric id: file URL, mime type, dimensions, alt text, caption, and the post it is attached to. Use this to read images or other media referenced by posts.
- Read
List error-log issues
Lists what is currently failing on this site: the PHP error log parsed into DISTINCT issues rather than raw lines, so a fatal that fired 400 times is one entry with count 400. Start every debugging investigation here. Each issue carries { signature, level, label, message, file, line, count, first_seen, last_seen, origin } where
originsays whose code it is ({ kind: plugin|mu-plugin|theme|core|unknown, slug, name, version }) andsignatureis the id you pass to get_log_issue and quote back to the user. Stack traces are NOT included, call get_log_issue for the one you are working on. Administrators with Developer mode on only. - Read
Get one error-log issue
Returns ONE issue from the error log in full, including its stack trace, by the
signatureyou got from list_log_issues. Call this on the issue you are actually investigating, the trace names the file and line where the failure started and the chain of calls that reached it, which is what you read the source at. The trace is verbatim server output: paths in it are real paths you may pass to read_source_excerpt. - Read
Read source around a logged line
Reads the PHP (or JS/CSS) source around a line the error log named, so you can see the code that failed instead of guessing at it. Pass a
filepath andlinetaken from an issue or from its stack trace. Returns numbered lines so you can quote them precisely. Limits, each returned as a refusal rather than an empty result: only files the current log mentions, only inside this WordPress install, only source extensions, and never wp-config.php or a .env (ask the user for any configuration value you need). Read-only: the file cannot be changed through any tool. - Read
Get site debugging context
Returns what this site is actually running: WordPress and PHP versions, the debug constants, the environment type, the active theme, and every active plugin with its version. Call this before proposing a fix, most WordPress errors are a version story ("that function was removed in PHP 8.1", "that plugin has not been updated since 2021"), and the answer is not in the log. Contains no credentials.
- Read
Search media
Searches the media library by title or file name and returns each item with where it is used:
used_in_count, and up to 5used_inrows with the post title andusedAs(featured image or content). Use it for "where is this image used?" or "have I used this photo a lot?". Pass one distinctive word asquery; an empty one lists the newest items. It only sees featured images and post content of posts the user can read, so never call an item unused from it: use find_unused_media. If has_more is true, call again with offset + 10. - Read
Find unused media
Lists the media library items nothing on the site points at, newest first, for "which images aren't used?" or "what can I delete?". It checks featured images, the content of every post, page, template and pattern in any status (drafts and trash too), widgets, the site logo and icon, the header and background images, and WooCommerce galleries. It cannot see custom fields, page-builder data kept outside post content, or files a theme or plugin loads from its own code, so a listed item is "not found anywhere I checked": say so, and leave deleting to the user.
totalis how many are unused out oflibrary_total. If has_more is true, call again with offset + 10. - Read
Search posts
Keyword-searches published WordPress blog posts by title and content (WordPress native search). Use this when the user is looking for content they or someone else wrote as a post or article: pass the key search terms as
query. Only for listing or counting questions ("how many posts do I have?") pass an emptyquery, which lists the newest posts (totalis the full count). Returns up to 10 matching posts with their title, a content excerpt, date, and URLs. If has_more is true, call again with the next offset. - Read
Search pages
Keyword-searches published WordPress pages (About, Contact, Services, Portfolio, etc.) by title and content. Use this when the user is looking for a static page, landing page, or informational page on the site. Pass the key search terms as
query. Returns up to 10 matching pages with their title, a content excerpt, and URLs. If has_more is true, call again with the next offset. - Read
Search comments
Keyword-searches approved WordPress comments by their text (WordPress native search), across all posts the requesting user is allowed to read, comments on private, draft, or password-protected posts the user cannot access are excluded. Use this when the user remembers something a reader said but does not know which post it was on: pass the distinctive words from the comment as
query. Also use it, with an emptyquery, for questions about the comments themselves, who has commented, the latest comments, how many there are (totalis the full count). Returns up to 10 matching comments with the commenter's name (author_name), an excerpt, parent post title, and URLs. If has_more is true, call again with the next offset. - Read
Search comments on a post
Keyword-searches approved comments on a SPECIFIC post by its WordPress ID (the post must be readable by the requesting user; an unreadable or nonexistent post returns an empty result). Use this when the user describes both a post and something a reader said on it: identify the post with search-posts, then pass its ID and the distinctive words of the comment as
query. More precise than search-comments whenever the parent post is known. Each match carries the commenter's name (author_name) and an excerpt. If has_more is true, call again with the next offset. - Read
List admin pages
Returns the full catalog of WordPress admin (wp-admin) destinations, pages for managing posts, categories, users, plugins, themes, settings, etc. Call this when the user asks "where can I find X?", "how do I get to Y?", "where are the settings for Z?", any navigational question about the admin UI. Each entry carries a title, url, icon, and description, so pick the few most relevant to the query. The catalog is small and stable so one call is enough.
- Read
Search WordPress.org plugins
Searches the official WordPress.org plugin directory. Use this when the user asks for a plugin recommendation, e.g. "is there a plugin for SEO?", "find me a backup plugin", "a caching plugin", "form builder". Returns up to 10 plugins with name, description, rating (0-100) and stars (0-5), active install count, and an admin URL that opens the plugin-info / install screen directly.
- Read
Read PHP error log
Reads the most recent entries from the site's PHP error log, typically wp-content/debug.log when WP_DEBUG_LOG is enabled, or the path set by the PHP error_log directive. Use this when the user asks "are there any errors?", "check the logs", "what went wrong?", or is troubleshooting a white screen / 500. Each entry is parsed into { timestamp, level, message } so you can summarise them. Administrators only.
- Read
Analyze comment for spam
Runs the AI spam/harm analysis for a single comment and returns its structured verdict ({ topic, ai_summary, harmful, spam }). On-demand only: nothing in the plugin runs it automatically.
Destructive 3
- Destructive
Update media details
Update metadata on a media library item (attachment): alt text, title, caption, and/or description. The file itself is never touched. Honours the edit capability on the attachment.
- Destructive
Create draft post
Create a NEW post or page as a DRAFT, authored by the calling user. The status is always draft: this ability can never publish. Use it to produce reviewable content (translations, variants, generated drafts) without touching any existing post.
contentis stored RAW, exactly as passed, so send block markup with its delimiter comments (<!-- wp:… -->) intact. - Destructive
Update post
Update fields on an existing post. Accepts any subset of title / content / excerpt / status.
contentis stored RAW, exactly as passed, so send block markup with its delimiter comments (<!-- wp:… -->) intact, passing rendered HTML would flatten the post's blocks. Honours the edit_post capability of the calling user.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install OpenStation and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. OpenStation registers its own abilities; this plugin discovers and governs them.
Open the Plugins’ own tools screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from OpenStation starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
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.
Frequently asked questions
Does OpenStation work with the Bridge?
Yes. OpenStation calls wp_register_ability() for 19 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Do OpenStation's abilities register automatically?
Yes, once OpenStation is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
Does OpenStation need anything special to work with the Bridge?
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.0), plus PHP 7.4 or later and the plugin active. Of the 19 abilities, 6 check 'read'; 2 check 'upload_files'; 2 check 'edit_post'; 1 check 'read_post'; 1 check 'edit_pages'; 1 check 'delete_others_posts'; 1 check 'manage_options'; 1 check 'moderate_comments'; for 4 the permission check runs through a helper or filter, so no single capability is listed here.
More AI & automation plugins
AI
ConditionalOnce 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 agent can list and read the Visualizer charts a user can manage, including each chart's type, columns, rows, options, data source and embed shortcode or block.
Verified from OpenStation's own free wordpress.org code (version 1.1.19) on 10 November 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, WordPress.org or OpenStation. Back to the full directory.
Bridge OpenStation, keep the same control.
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.