Once enabled, an agent could discover and preview Templately's cloud template library, inspect a full-site pack before importing it, import a template into a new or existing page, save a template to the library, and track, retry, or revert a full-site import in progress.
View Templately on WordPress.org
Needs WordPress 6.9 or newer with the Abilities API, Templately active, and its wp-abilities-api bridge module turned on, which is not the default state in the current release. Every ability checks manage_options, and inserting a template into an existing post additionally requires edit_post on that specific post.
Grouped by what each one can change. Every one starts off until you enable it.
Searches or browses Templately's cloud library of full-page and section designs for Elementor or Gutenberg.
Returns full detail for one library template, including whether its dependencies are ready on this site.
Inspects a full-site template pack before importing it.
Reports whether the site has a connected Templately account for the acting user.
Returns a URL to connect the site to a Templately account through Google sign-in; annotated readonly even though completing it links a real account.
Reports progress of an in-progress full-site import.
Retries a failed step of a full-site import.
Connects the site to a Templately account using an account API key.
Imports one library template as a brand-new WordPress page.
Merges one library template's content into an existing post.
Saves one library template into the site's own Templately library for later reuse.
Starts importing a full-site template pack, replacing site content.
Reverts a completed full-site import.
Signs the site out of its connected Templately account.
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. Templately 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 Templately 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. Templately's wp-abilities-api bridge module registers all 14 of its native MCP abilities through wp_register_ability() with real readonly/destructive annotations, but the module is deliberately held back in 3.8.0 behind a deferred-module flag that defaults off, so the abilities do not register on a stock install of the current release.
The TEMPLATELY_ENABLE_DEFERRED_MODULES constant, or the templately_deferred_module_enabled filter, must resolve true; neither is set by default in the 3.8.0 release, so the bridge module does not boot and no abilities register. Even once enabled, most abilities also need the site connected to a Templately account (API key or Google sign-in) to do anything useful, though the auth abilities themselves work without one.
Needs WordPress 6.9 or newer with the Abilities API, Templately active, and its wp-abilities-api bridge module turned on, which is not the default state in the current release. Every ability checks manage_options, and inserting a template into an existing post additionally requires edit_post on that specific post.
An agent can read and edit the structure of Elementor-built pages, list and inspect widget and component schemas, manage the site's shared global CSS classes and design-token variables, build whole page layouts from a composition description, and publish or preview documents.
Once enabled, an agent can read and manage HFE header/footer/block templates and Elementor pages end to end: list, create, update, duplicate, delete and restore templates and pages, build and edit Elementor layouts widget by widget, toggle widgets and extensions, set display rules and theme compatibility, read the site's design tokens, and clear the Elementor CSS cache.
An agent can list and insert ElementsKit's widgets and templates into Elementor pages, scaffold new pages, headers, footers and custom widgets, and manage mega menus, all with an unauthenticated caller in mind since the code carries no readonly or destructive annotations.
Verified from Templately'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, WPDeveloper or Templately. 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.