An agent can read and write posts, pages, categories, tags, WooCommerce products and their taxonomies, Elementor page and template HTML, Polylang translation links, and (with a Pro license and Google Site Kit active) Search Console and GA4 traffic data.
View WDS MCP Content Manager on WordPress.org
Needs WordPress 6.9 or newer with the plugin active; a WDS MCP Pro license is needed for the WooCommerce, Elementor, Polylang, Site Kit, content-graph, and featured-image abilities to actually execute (they still register on the Free tier but return an upgrade-required error). Plain read abilities like get-posts, get-pages, get-categories, get-tags, get-products, and the translation-reading calls use no capability check at all (permission_callback returns true), while writes need wds_can_write_post, wds_can_write_page, wds_can_manage_categories, wds_can_manage_product_terms, wds_can_manage_terms, wds_can_edit_posts, wds_can_upload_files, or wds_can_manage_options depending on the group.
The full source shows two corrections to the earlier pass. First, several abilities (create-category, update-category, create-tag, update-tag, create-product-category, update-product-category, create-product-tag, update-product-tag, upload-image, set-post-language, link-translations, set-term-language, link-term-translations, set-featured-image) declare only 'readonly' => false in their annotations with no 'destructive' key at all; the draft had marked these 'write', but the rule requires an EXPLICIT 'destructive' => false for that, so they are corrected to 'destructive' here. Second, set-featured-image and the four site-kit abilities were marked 'unknown'/truncated in the draft; the full file shows they all use wds_can_edit_posts or wds_can_manage_options and either an explicit partial annotation or none at all, so all five are now filled in rather than left unknown.
Grouped by what each one can change. Every one starts off until you enable it.
Lists blog posts.
Returns full details of a single post including content, taxonomies, and Yoast SEO meta.
Reads an Elementor page or template's stored data.
Creates a new blog post with optional categories, tags, featured image, and Yoast SEO meta.
Updates an existing blog post.
Runs Yoast SEO's internal indexing routine after bulk SEO meta changes.
Creates a new page with optional slug, parent, template, and Yoast SEO meta.
Updates an existing page.
Scans published content to build a content knowledge graph with PageRank and topic clusters.
Creates a WooCommerce product with price, files, taxonomies, and Yoast SEO meta.
Updates an existing WooCommerce product.
Sets the JSON-LD schema for a product.
Sets an Elementor page's stored HTML.
Injects Elementor section JSON into a page.
Creates a new Elementor Library template with optional JSON content and Theme Builder display conditions.
Lists pages.
Lists post categories.
Creates a new post category.
Updates an existing post category.
Deletes an existing post category.
Lists post tags.
Creates a new post tag.
Updates an existing post tag.
Deletes an existing post tag.
Writes nodes and edges into the plugin's content knowledge graph.
Reads back computed content-graph insights.
Lists WooCommerce products.
Returns full details of a single WooCommerce product including taxonomies and Yoast SEO meta.
Lists WooCommerce product categories.
Creates a WooCommerce product category.
Updates a WooCommerce product category.
Deletes a WooCommerce product category.
Lists WooCommerce product tags.
Creates a WooCommerce product tag.
Updates a WooCommerce product tag.
Deletes a WooCommerce product tag.
Lists saved Elementor Library templates.
Updates an Elementor template.
Sets an Elementor Library template's content from a raw HTML string.
Sets a post or page's Elementor content from a raw HTML string.
Uploads an image into the Media Library by URL or base64 data.
Sets a post's Polylang language.
Links posts as Polylang translations of each other.
Returns the Polylang translation map for a post or page.
Sets a taxonomy term's Polylang language.
Links taxonomy terms as Polylang translations of each other.
Returns the Polylang translation map for a taxonomy term.
Sets an existing Media Library attachment as the featured image of a post.
Returns the top Google Search Console queries driving traffic to the site or a page.
Returns the pages with the most GA4 sessions over a date range.
Returns combined Search Console and GA4 metrics for a single URL.
Returns a site-wide GA4 traffic summary by channel.
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. WDS MCP Content Manager 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 WDS MCP Content Manager 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 52 abilities in the core Abilities API with meta.mcp.public set on all of them, so the Bridge can discover and wrap any that the site owner has not individually disabled through the plugin's own settings.
Any ability can be removed from the registry through the 'wds_mcp_permissions' option, which stores a list of disabled ability ids. For every ability past the first 17 (the WooCommerce, Elementor, Polylang, and Site Kit ones, plus build-content-graph, get-content-insights, and set-featured-image), the registration guard is written as '! is_pro || ! disabled', which is an OR: on the Free tier this is always true regardless of the disabled list, so the disabled setting has no effect on these abilities unless the site holds a Pro license. None of the WooCommerce, Elementor, Polylang, or Site Kit abilities check that their companion plugin is actually active before registering; that check only happens inside the execute_callback at call time, so on a site without WooCommerce (for example) those abilities still appear in the registry and simply error when run. On the Free tier, every one of the 34 abilities gated by '$is_pro' still registers normally but its execute_callback is swapped for a stub that returns a 403 pro_required error naming the upgrade URL, instead of the real handler.
Needs WordPress 6.9 or newer with the plugin active; a WDS MCP Pro license is needed for the WooCommerce, Elementor, Polylang, Site Kit, content-graph, and featured-image abilities to actually execute (they still register on the Free tier but return an upgrade-required error). Plain read abilities like get-posts, get-pages, get-categories, get-tags, get-products, and the translation-reading calls use no capability check at all (permission_callback returns true), while writes need wds_can_write_post, wds_can_write_page, wds_can_manage_categories, wds_can_manage_product_terms, wds_can_manage_terms, wds_can_edit_posts, wds_can_upload_files, or wds_can_manage_options depending on the group.
An agent can discover ACF field groups, custom post types, and custom taxonomies that the site owner has opted into AI access, then list, read, create, update, and delete items of those content types along with their custom field values.
An agent can list and inspect tables, charts and media on the site, read the plugin's system info, licence tier and changelog, and create or edit Simple tables and charts, upload images from a URL, and update table, chart, or global plugin settings.
An agent can list, read, create, update and delete docs, doc categories/tags/glossary terms, FAQs and FAQ groups, attach FAQ groups to a doc, read per-doc view analytics, read the plugin's status, and read or update its settings.
Verified from WDS MCP Content Manager'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, wallstrdev or WDS MCP Content Manager. 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.