Lets an agent query and search the log of MCP tool activity on the site, pull usage statistics and error analysis, review and acknowledge security-relevant events, send a test alert, and clear old or all logged entries.
View MCP Logs on WordPress.org
Needs WordPress 6.9 or later with the plugin active. Every ability requires the manage_options capability, checked directly with no plugin-specific role layered on top.
All twelve abilities were read from the full source with no meta.annotations block on any of them, so each defaults to destructive under the fail-safe risk rule regardless of what the ability actually does.
Grouped by what each one can change. Every one starts off until you enable it.
Returns logged MCP tool activity entries.
Returns aggregate statistics about MCP tool usage.
Returns the logged activity for one MCP session.
Searches the activity log by keyword or filter.
Summarizes recent errors seen in MCP tool calls.
Returns performance metrics per MCP tool.
Deletes log entries older than a given age.
Returns security-relevant events such as velocity, destructive-tool, or error-storm alerts.
Returns aggregate statistics on security events.
Marks a security event as acknowledged.
Sends a test security alert to confirm alerting is configured.
Deletes every logged entry; the plugin's own input schema requires an explicit confirm flag because this is a destructive action.
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. MCP Logs 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 Logs 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. All twelve abilities register in the core Abilities API, so the Bridge can discover and wrap them once an operator enables this plugin's namespace.
Yes, unconditionally, once MCP Logs is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or later with the plugin active. Every ability requires the manage_options capability, checked directly with no plugin-specific role layered on top.
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 Logs'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, Riaan K. or MCP Logs. 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.