An agent can pull a paginated log of MCP and AI tool interactions the site has recorded, filtered by tool name, user, or date range.
View MCP Tracker on WordPress.org
Needs WordPress 6.9 or newer with MCP Tracker active. The single ability requires manage_options.
The ability carries no annotations array at all, so per the read/write/destructive rule (no annotations defaults to destructive) it is marked destructive even though the operation only reads a log; the plugin's own code never declares it read-only.
Grouped by what each one can change. Every one starts off until you enable it.
Retrieves a paginated log of recorded MCP and AI interactions, filterable by tool, user, and date range.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. MCP Tracker 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 MCP Tracker 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. It registers one ability in the core Abilities API with no meta.mcp.public requirement, so the Bridge can discover and wrap it once enabled.
Yes, unconditionally, once MCP Tracker is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or newer with MCP Tracker active. The single ability requires manage_options.
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 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.
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.
Verified from MCP Tracker'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, WPVibes or MCP Tracker. 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.