wallstrdev

WDS MCP Content Manager connects your WordPress site to AI agents (Claude, Cursor, and other MCP-compatible clients) so they can read, create, and manage your content through natural language prompts.
<h4>How it works</h4>
The plugin registers a set of abilities on top of the <a href="https://github.com/WordPress/mcp-adapter" rel="nofollow ugc">WordPress MCP Adapter</a>. Once installed, your AI agent can list posts, create content, manage categories and tags, upload images, and more — all without leaving your AI client.
<h4>Free abilities (no license required)</h4>
<ul>
<li>wds/get-posts — List published posts with title, URL, date, and excerpt</li>
<li>wds/get-post — Fetch full post content, categories, tags, and SEO meta</li>
<li>wds/create-post — Create a post with categories, tags, and featured image</li>
<li>wds/update-post — Update any field of an existing post</li>
<li>wds/reindex-yoast-seo — Run Yoast SEO data optimization (indexables reindex) after bulk SEO updates</li>
<li>wds/get-pages — List pages with URL, status, parent, and template</li>
<li>wds/create-page — Create a page with slug, parent, template, and featured image</li>
<li>wds/update-page — Update page content, status, slug, hierarchy, and template</li>
<li>wds/get-categories — List all post categories</li>
<li>wds/create-category — Create a new post category</li>
<li>wds/update-category — Update an existing post category</li>
<li>wds/delete-category — Delete an existing post category</li>
<li>wds/get-tags — List all post tags</li>
<li>wds/create-tag — Create a new post tag</li>
<li>wds/update-tag — Update an existing post tag</li>
<li>wds/delete-tag — Delete an existing post tag</li>
</ul>
<h4>Pro abilities (requires a Pro license)</h4>
<ul>
<li>wds/get-products — List WooCommerce products with pricing and status</li>
<li>wds/get-product — Fetch full WooCommerce product details and taxonomy terms</li>
<li>wds/create-product — Create a WooCommerce product with pricing and downloads</li>
<li>wds/update-product — Update any field of an existing WooCommerce product</li>
<li>wds/get-product-categories — List WooCommerce product categories</li>
<li>wds/create-product-category — Create a WooCommerce product category</li>
<li>wds/update-product-category — Update a WooCommerce product category</li>
<li>wds/delete-product-category — Delete a WooCommerce product category</li>
<li>wds/get-product-tags — List WooCommerce product tags</li>
<li>wds/create-product-tag — Create a WooCommerce product tag</li>
<li>wds/update-product-tag — Update a WooCommerce product tag</li>
<li>wds/delete-product-tag — Delete a WooCommerce product tag</li>
<li>wds/set-product-schema — Inject JSON-LD structured data into the page head</li>
<li>wds/set-elementor-page — Inject a full HTML design via Elementor Canvas</li>
<li>wds/inject-elementor-json — Inject native Elementor sections JSON</li>
<li>wds/upload-image — Sideload an image from URL into the Media Library</li>
<li>wds/set-featured-image — Set or remove the featured image on a post</li>
<li>wds/set-post-language — Set Polylang language on a post</li>
<li>wds/link-translations — Link posts as Polylang translation pairs</li>
<li>wds/set-term-language — Set Polylang language for taxonomy terms</li>
<li>wds/link-term-translations — Link taxonomy terms as Polylang translation pairs</li>
<li>wds/get-term-translations — Get Polylang translation map for a taxonomy term</li>
<li>site-kit/get-top-queries — Returns top Google Search Console queries for the site (requires Google Site Kit plugin)</li>
<li>site-kit/get-top-pages — Returns top pages by traffic from Google Analytics 4 (requires Google Site Kit plugin)</li>
<li>site-kit/get-page-performance — Returns combined Search Console + GA4 metrics for a single URL (requires Google Site Kit plugin)</li>
<li>site-kit/get-traffic-overview — Returns site-wide traffic summary by channel from GA4 (requires Google Site Kit plugin)</li>
</ul>
Pro licenses are available at <a href="https://wallstrdev.de/product/wds-mcp-content-manager-pro/" rel="nofollow ugc">wallstrdev.de</a>.
<h4>Requirements</h4>
<ul>
<li>WordPress 6.3 or later</li>
<li><a href="https://github.com/WordPress/mcp-adapter" rel="nofollow ugc">WordPress MCP Adapter</a> plugin (free, required)</li>
<li>WooCommerce — optional, needed for product abilities</li>
<li>Elementor — optional, needed for Elementor abilities</li>
<li>Polylang — optional, needed for multilingual abilities</li>
</ul>
<h3>External Services</h3>
<h4>WordPress MCP Adapter</h4>
If the WordPress MCP Adapter plugin is not installed, an admin notice offers a one-click install button. Clicking it downloads the adapter from:
<pre><code>https://github.com/WordPress/mcp-adapter/releases/latest/download/mcp-adapter.zip
</code></pre>
This is the official plugin from the WordPress GitHub organisation. The download is triggered only by an explicit admin click — nothing is downloaded automatically.
<h4>WDS License Server</h4>
This plugin connects to an external license validation service only when a Pro license key is entered.
Service: WDS License Server, operated by Wallstrdev (https://wallstrdev.de)
When it is called: 
– When you save a Pro license key under Settings → WDS MCP Setup → License 
– Once per day (in the background on admin_init) to revalidate the key
What is sent: 
– Your license key 
– Your site domain (e.g. example.com)
What is NOT sent: post content, user data, personally identifiable information, or site configuration.
Why: To confirm the license key is valid for your domain and determine your plan tier (free vs. pro).
Data policy: <a href="https://wallstrdev.de/privacy-policy/" rel="nofollow ugc">wallstrdev.de/privacy-policy/</a>
Free users (no license key entered) never trigger any external HTTP request.
<h4>Google Search Console API</h4>
The Pro abilities <code>site-kit/get-top-queries</code> and <code>site-kit/get-page-performance</code> call the Google Search Console API directly on behalf of the site owner.
Service: Google Search Console API, provided by Google LLC (<code>https://searchconsole.googleapis.com</code>)
When it is called: Only when an AI agent explicitly invokes the <code>site-kit/get-top-queries</code> or <code>site-kit/get-page-performance</code> Pro ability. Requires the Google Site Kit plugin to be installed, activated, and connected to Search Console.
What is sent: 
– Your Search Console property URL (your site’s domain) 
– Query parameters: date range, dimensions (query/page), row limit 
– An OAuth 2.0 Bearer token retrieved from the Site Kit plugin’s stored credentials — no token is stored or transmitted by this plugin
What is NOT sent: post content, user data, passwords, or any personally identifiable information beyond the site URL.
Why: To retrieve search query and page performance data from Google Search Console so the AI agent can analyse your organic search traffic.
Google Terms of Service: https://developers.google.com/terms 
Google Privacy Policy: https://policies.google.com/privacy
<h4>Google Analytics Data API</h4>
The Pro abilities <code>site-kit/get-top-pages</code>, <code>site-kit/get-page-performance</code>, and <code>site-kit/get-traffic-overview</code> call the Google Analytics Data API directly on behalf of the site owner.
Service: Google Analytics Data API, provided by Google LLC (<code>https://analyticsdata.googleapis.com</code>)
When it is called: Only when an AI agent explicitly invokes one of the above Pro abilities. Requires the Google Site Kit plugin to be installed, activated, and connected to a Google Analytics 4 property.
What is sent: 
– Your GA4 numeric property ID 
– Query parameters: date range, metrics (sessions, pageviews, etc.), dimensions (pagePath, sessionDefaultChannelGroup, etc.), row limit 
– An OAuth 2.0 Bearer token retrieved from the Site Kit plugin’s stored credentials — no token is stored or transmitted by this plugin
What is NOT sent: post content, visitor PII, passwords, or any data beyond the analytics query parameters listed above.
Why: To retrieve traffic and engagement metrics from Google Analytics 4 so the AI agent can summarise your site’s performance.
Google Terms of Service: https://developers.google.com/terms 
Google Privacy Policy: https://policies.google.com/privacy

WDS MCP Content Manager

Give your AI agent full control of your WordPress site via the Model Context Protocol (MCP).

interconnectit

Spectacula

cm2creative

Here at interconnect/it we have a policy of developing client sites with the premise of “content manage everything!” That means the little notices on sites, minor widgets and so on should not only be content managed, but they should be easy for both an end-user and a developer to work with.
To that end, we developed Spots. This creates a custom post type that allows you to create widgets using a visual editor, whilst also giving developers an easy hook for the creation of content managable elements within a theme.
The plugin now uses caching in order to help ensure that the load on a typical site is kept to a minimum. Performance is important!
The plugin is prepared for translation, if you’d like to drop us a line about your translation you can contact us through our <a href="http://interconnectit.com/about/contact/" rel="nofollow ugc">website</a>.
<h3>Developer Notes</h3>
Spots provides 2 template tags for developers to use shown below with their supported arguments.
<pre><code>icit_spot( $id_or_name, $template );
</code></pre>
<ul>
<li><code>$id_or_name</code>: Required. A numeric ID or the name of a spot as a string.</li>
<li><code>$template</code>: Optional. A string used in a call to <code>get_template_part()</code></li>
</ul>
This template tag always echos out the spot.
<pre><code>icit_get_spot( $id_or_name, $template, $echo );
</code></pre>
Same as the above with an extra argument:
<ul>
<li><code>$echo</code>: Optional. Defaults to false. A boolean to indicate whether to echo the spot content or just return it.</li>
</ul>
<h4>Basic Usage</h4>
You can use spots to replace boilerplate text in your themes. If you have areas in your themes where typically you would hard code the text you could use the following code:
<pre><code><?php
if ( function_exists( 'icit_spot' ) )
 icit_spot( 'Copyright' );
?>
</code></pre>
The above code would output the contents of a spot titled ‘Copyright’. If the spot does not exist it will be created as a draft. Spots in draft mode are only visible to logged in users with editing capabilities.
<h4>Templates</h4>
The plugin will initially look for a file in your theme using the <code>get_template_part()</code> function. If you have a file called <code>spot.php</code> in your theme that will be the default template for all spots. The <code>icit_spot()</code> function can take a second parameter for the template part to use for example:
<pre><code><?php
if ( function_exists( 'icit_spot' ) )
 icit_spot( 'Copyright', 'copyright' );
?>
</code></pre>
The above code will make the plugin look in your theme folder for a file called <code>spot-copyright.php</code> to use for the output. If not available it will fall back to <code>spot.php</code> and if that is not available it will simply output the spot contents.
Use templates when you want to display a featured image from a spot or if you require some additional/alternative markup for the spot. Spots are just like posts, so in the templates you retrieve the contents of the spot using <code>the_content()</code> just as would in the loop.
Basic spot template example:
<pre><code><div class="spot">
 <?php the_content(); ?>
</div>
</code></pre>
Spot template with featured image:
<pre><code><div class="spot-with-image">
 <?php
 if ( has_post_thumbnail() )
 the_post_thumbnail( 'medium' );
 the_content(); ?>
</div>
</code></pre>
<h4>Additional</h4>
There are many filters and hooks available to get even more out of spots so drop by the plugin homepage or use the forums if there is something you need to do with spots but aren’t sure how.

Spots

Default install on every site

Content manage those little snippets of text that you need across your WordPress site and in widgets properly. Forget the text widget.

WDS MCP Content Manager vs Spots