An agent can search and read the activity log, alerts, connectors, exclusion rules, and settings, and can create alerts and exclusion rules, update settings, delete an alert, or purge log records once a human has enabled write access.
Stream must be installed, active, and have its own Enable Abilities API setting turned on, on WordPress 6.9 or newer. The six read abilities are gated by the view_stream capability (normally editors and admins), while the five write and delete abilities require Stream's settings capability, which defaults to manage_options and additionally needs manage_network_options on a network-activated multisite.
Matches easymcpai's listed count of 11; verified directly from Abilities::get_ability_slugs().
Grouped by what each one can change. Every one starts off until you enable it.
Returns a filtered, paginated list of Stream activity log entries.
Returns full details for one Stream activity log entry.
Returns the current Stream plugin configuration.
Returns the configured Stream alert rules, with destination credentials redacted.
Returns the available Stream connectors and their context/action labels.
Returns the rules that keep matching events out of the activity log.
Creates a new Stream alert rule with a destination and trigger conditions.
Updates Stream's plugin configuration, including network-wide settings on multisite.
Adds a rule that stops matching events from being logged going forward.
Permanently deletes activity log records matching the given criteria; requires an explicit confirm flag.
Permanently deletes a Stream alert rule.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Stream registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Stream starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
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.
Yes. Stream registers 11 real abilities behind its own WordPress 6.9 check and capability gates, so the Bridge can wrap and expose them once an operator enables both Stream's own toggle and the individual bridge switch.
Stream's own 'Enable Abilities API' toggle, in the plugin's Advanced settings, must be turned on; abilities are not registered while it is off.. Stream also checks for the WP_Ability class before registering anything, so it will not register on a site below WordPress 6.9 even though the readme lists a lower minimum..
Stream must be installed, active, and have its own Enable Abilities API setting turned on, on WordPress 6.9 or newer. The six read abilities are gated by the view_stream capability (normally editors and admins), while the five write and delete abilities require Stream's settings capability, which defaults to manage_options and additionally needs manage_network_options on a network-activated multisite.
An agent can read Burst's analytics dashboard: live visitors, live traffic, a daily summary, page and referrer datatables, onboarding tasks, tracking health, and, with Burst Pro, ecommerce sales and subscription figures, all without writing anything back.
An agent can read the plugin's tracking status, debug info, and full settings schema for Google Ads, GA4, Meta and TikTok pixels, and update those settings or configure a specific pixel in one call.
An agent can look up how many times a specific post has been viewed, in total or over a day, week, or month, and pull a ranked list of the site's most-viewed posts or products.
Verified from Stream's own free wordpress.org code on 28 September 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, XWP or Stream. Back to the full directory.
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.