An agent can list and read galleries, list gallery layouts and their setting schemas, search the media library for attachments, create a new gallery from attachment IDs, and update an existing gallery's settings, layout, or attachment list.
View FooGallery on WordPress.org
FooGallery must be active with WordPress 6.9 or newer. Reading abilities check the edit_foogalleries capability (or edit_post for a specific gallery), media search checks upload_files, and creating or updating a gallery checks create_foogalleries or edit_post, with publish_foogalleries checked additionally when the status is set to publish.
Grouped by what each one can change. Every one starts off until you enable it.
Lists FooGallery galleries, filterable by search text, status, and layout.
Returns one FooGallery gallery by its ID.
Returns the normalized setting field schema for one gallery layout.
Lists registered FooGallery gallery layouts and optionally their setting fields.
Searches media library attachments by title, caption, alt text, URL, or taxonomy terms.
Creates a new gallery from a list of media library attachment IDs.
Updates an existing gallery's title, status, layout, settings, sort mode, or custom CSS.
Replaces, appends, or removes attachments on an existing gallery.
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. FooGallery 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 FooGallery 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 eight abilities through wp_register_ability unconditionally once WordPress 6.9's Abilities API is present, covering galleries, layouts, attachments, and media search.
Yes, unconditionally, once FooGallery is active. Nothing else has to be configured for the Bridge to discover them.
FooGallery must be active with WordPress 6.9 or newer. Reading abilities check the edit_foogalleries capability (or edit_post for a specific gallery), media search checks upload_files, and creating or updating a gallery checks create_foogalleries or edit_post, with publish_foogalleries checked additionally when the status is set to publish.
An agent can check an image's optimization status, quota and account plan, optimize or restore a specific media item, kick off a bulk optimization run, read or update Imagify's settings, and queue missing WebP/AVIF generation.
An agent can add YouTube, Vimeo, or self-hosted videos to the media library, look up, update, or delete existing video records and their shortcodes, manage chapter markers, and read or change Presto Player's global settings.
An agent can scan a site for external or broken (404) images, start or stop the background import that downloads and rewrites them locally, check import progress and stats, and wipe the stored statistics and cache.
Verified from FooGallery'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, FooPlugins or FooGallery. 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.