Once enabled, an AI agent can read a site traffic overview, top content by type (posts, referrers, search terms, and more), per-post view history, a visits timeseries, follower counts, and the current Stats visibility settings, and can update who can view or is counted by Stats.
View Jetpack Search on WordPress.org
Needs Jetpack Search active on WordPress 6.9 or later, connected to WordPress.com, with the jetpack_wp_abilities_enabled filter switched on (off by default). The six read abilities check the view_stats capability; update-settings checks manage_options.
Grouped by what each one can change. Every one starts off until you enable it.
Returns a single snapshot of today's views/visitors, week/month totals, posting streak, top post, and top referrer.
Returns the top items for a chosen content type (posts, referrers, search terms, clicks, tags, authors, countries, downloads, or video plays).
Returns view history for a single post: total views and a per-period timeseries.
Returns a site-level views/visitors/likes/comments timeseries.
Returns a breakdown of follower counts across email, WordPress.com, comments, and Publicize services.
Reads who can see Stats, whose visits are counted, and the Do Not Track setting.
Updates one or more Stats settings: admin bar visibility, viewer roles, counted roles, or Do Not Track.
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. Jetpack Search 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 Jetpack Search 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.
Conditionally. Jetpack Search's own plugin bootstrap activates Automattic's vendored Jetpack Stats package, whose 7 abilities register through the shared jetpack-wp-abilities Registrar, but that registrar is gated behind the jetpack_wp_abilities_enabled filter, which defaults to false. A vendored Jetpack Connection abilities registrar also ships in the plugin's dependencies but its init() method is never called anywhere in the source, so it never registers regardless of the filter.
The jetpack_wp_abilities_enabled filter must return true; it defaults to false so nothing registers on a stock install.. The site must be connected to WordPress.com for the Stats abilities to return real data once registration is enabled..
Needs Jetpack Search active on WordPress 6.9 or later, connected to WordPress.com, with the jetpack_wp_abilities_enabled filter switched on (off by default). The six read abilities check the view_stats capability; update-settings checks manage_options.
An AI agent can list and read boards, stages, and tasks (including a personal task list and a cross-board search), then create, update, move, assign, archive, comment on and label tasks, and manage stages and labels.
An AI agent can send a text message, with an optional inline button, to the site's configured Telegram chat.
An agent can read and manage CRM contacts, log notes and calls, read and reply to support tickets, read bookings, automations, campaigns, and message history, read and write invoices and proposals, and read and mark the caller's own notifications, scoped to whichever modules the site owner has active.
Verified from Jetpack Search'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, Automattic or Jetpack Search. 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.