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.
View Presto Player on WordPress.org
Needs WordPress 6.9 or newer with Presto Player active, plus the plugin's own AI-access toggle turned on in its settings. Video and chapter abilities check edit_posts or publish_posts depending on the action, delete-video checks delete_posts, and the two settings abilities check manage_options.
Grouped by what each one can change. Every one starts off until you enable it.
Returns one video record by ID.
Returns videos from the Media Hub, optionally filtered by tag.
Returns the embeddable shortcode for a reusable video post.
Returns the chapter markers defined on a video.
Derives chapter markers from a WebVTT caption track without writing anything.
Returns the plugin's global player, branding, and analytics settings.
Adds a YouTube video to the Media Hub from its URL.
Adds a Vimeo video to the Media Hub from its URL.
Adds a self-hosted MP4 or HLS video from an upload, a file URL, or an existing Media Library attachment.
Updates the fields and tags of an existing video record.
Writes one Presto Player global option group.
Trashes a video record by ID.
Replaces the full chapter list on a video.
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. Presto Player 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 Presto Player 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. Presto Player registers a clean set of video, chapter, and settings abilities in the core Abilities API with explicit readonly/destructive annotations, so the Bridge can classify and expose each one correctly.
A master 'enable abilities' toggle in Presto Player's own settings must be on for any ability, read or write, to register.. A separate 'allow AI to make changes' toggle must also be on before write or destructive abilities (create, update, delete video, save chapters, update settings) register; read-only abilities register on the master toggle alone..
Needs WordPress 6.9 or newer with Presto Player active, plus the plugin's own AI-access toggle turned on in its settings. Video and chapter abilities check edit_posts or publish_posts depending on the action, delete-video checks delete_posts, and the two settings abilities check manage_options.
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 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.
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 Presto Player'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, Andre Gagnon or Presto Player. 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.