WordPress

What you can do

This is the widest platform MCP Ads supports because WordPress itself is a platform of plugins, not one fixed feature set. Claude works across core WordPress, Elementor, WooCommerce and whatever plugins the site actually runs. The registry currently lists over 1,800 tools, and the prefixes tell you which layer each one touches: wp_ for core, elementor_ for the page builder, woo_ for WooCommerce, seo_ and rankmath_ and aioseo_ for the SEO layer, and a plugin's own name for the rest.

• Publish, edit and audit content across posts, pages, media, menus and users
• Build Elementor layouts: hero, features, pricing, FAQ and testimonial sections, or a whole landing page from a brief
• Run WooCommerce: products, variations, orders, coupons, shipping zones and store analytics
• Audit and fix SEO: missing meta, duplicate titles, thin content, redirects, schema and sitemaps
• Run accessibility checks for alt text, heading hierarchy, contrast and form labels
• Operate the specific plugins a site has installed, from Amelia bookings to LearnDash courses to FluentCRM

Connect the site

MCP Ads normally talks to WordPress over its REST API using an Application Password, generated once in wp-admin. Most sites need nothing more than that: a site URL, a WordPress username and the password. Nothing has to be installed.

1. Create an Application Password

   In wp-admin go to Users → Profile, scroll to Application Passwords, give the new password a name such as "MCP Ads" and click Add. WordPress shows the password once, with spaces in it. Copy the whole thing; the spaces are fine to keep or remove, but the characters between them must be exact.

2. Check the user's role

   The connection can do exactly what that WordPress user can do, no more. An Editor can write posts but cannot install plugins or change WooCommerce settings; an Administrator can do everything. Use a dedicated Administrator user for MCP Ads if you want the full surface, and a lower role if you want to cap what Claude can touch.

3. Enter the details in Connections

   Open the MCP Ads dashboard, choose WordPress, and enter the site URL (including https://), the username and the Application Password. The connection is tested against the live site before it is saved, so a wrong password fails here rather than on first use.

4. Ask for something real

   A read-only first prompt that proves the connection, the role and the plugin detection all work.

   Try this firstCopy

   Which SEO plugin is my WordPress site running? Then list
   the ten most recent posts and flag any that are missing
   a meta description or a focus keyword.

Sites behind Cloudflare or another firewall

Some hosts and CDNs block /wp-json/ and xmlrpc.php outright, which is where the REST API lives. For those sites, install the free MCP Ads Connector plugin from the connection screen in the dashboard. It answers over admin-ajax.php instead, which firewalls almost never block, and hands each request straight to WordPress's own REST router underneath, so every normal permission check still applies.

• Standard sites: URL, username and Application Password, no plugin required
• Firewalled sites: the same three details plus the MCP Ads Connector plugin
• The plugin is not a new API surface; it accepts a REST method and route and passes them to WordPress's own request handler
• Neither path can bypass an IP-level block. If the firewall refuses this server's address entirely, that has to be allowed at the firewall, not fixed in the plugin

Representative tools

Generated from the live server registry. These are real tool names Claude can call today; the full list, grouped by plugin, is in the reference.

Safety on this platform

Troubleshooting

• The Application Password is rejected on a site where you know it is right: a security plugin (Wordfence, iThemes, Solid Security) or the host may have disabled Application Passwords or REST authentication. Look for a setting named "REST API" or "Application Passwords" in that plugin and enable it, or install the MCP Ads Connector plugin.
• The connection test fails with a 403 or a Cloudflare challenge page: the firewall is blocking /wp-json/. Install the MCP Ads Connector plugin and reconnect; it routes around the block using admin-ajax.php.
• The password was pasted with extra characters: copying from wp-admin sometimes picks up a trailing space or line break, and some password managers strip the internal spaces and then add their own. Paste the password into a plain text field first, check it has 24 letters in six groups of four, and try again.
• Claude says a tool is not permitted: the user's role is too low for that action. Editors cannot manage plugins, users or WooCommerce settings; Shop Managers cannot edit pages. Reconnect with an Administrator, or accept the limit if it was intentional.
• Elementor or WooCommerce tools report the plugin is not installed on a site where it is: run the detect tool for that plugin first. Some hosts cache REST responses aggressively; clearing the site cache and retrying usually fixes it.

Go further

All WordPress tools

Every core, Elementor, WooCommerce, SEO and plugin tool with its parameters.

Search Console

Pair site edits with the search data that motivated them.

SEO skills

Sitemap audits, error monitoring and CTR workflows that end in WordPress edits.