WordPress MCP Server

What a call looks like

These are real tool names from the live server, with the shape of what they return.

[
  { "id": 412, "date": "2026-10-14T09:12:40", "status": "draft", "slug": "spring-pruning-guide",
    "title": { "rendered": "Spring Pruning Guide" }, "categories": [7] },
  { "id": 409, "date": "2026-10-11T16:03:11", "status": "draft", "slug": "best-hedge-trimmers",
    "title": { "rendered": "Best Hedge Trimmers for Small Gardens" }, "categories": [7, 12] }
]

{
  "updated": true,
  "plugin": "Rank Math",
  "id": 412,
  "type": "post",
  "fields": ["rank_math_description", "rank_math_focus_keyword", "rank_math_title"]
}

[
  { "id": 10482, "number": "10482", "status": "processing", "date_created": "2026-10-17T08:41:02",
    "total": "129.00", "payment_method_title": "Credit card",
    "line_items": [{ "name": "Winter Jacket", "quantity": 1, "total": "119.00" }] },
  { "id": 10479, "number": "10479", "status": "processing", "date_created": "2026-10-16T19:22:57",
    "total": "54.50", "payment_method_title": "PayPal",
    "line_items": [{ "name": "Wool Beanie", "quantity": 2, "total": "44.50" }] }
]

{
  "id": 2211,
  "name": "Winter Jacket",
  "status": "publish",
  "regular_price": "119.00",
  "sale_price": "89.00",
  "on_sale": true
}

What it covers

The tool prefixes tell you which layer of the site a call touches, and they are worth knowing because they make prompts land in one call. Every name below is a real tool; the full list is in the WordPress tool reference.

• Core content — wp_list_posts, wp_get_post, wp_create_post, wp_update_post, wp_create_page, wp_duplicate_post, wp_bulk_update_posts, plus media, menus, categories, tags, users and comments
• SEO — seo_meta_set_universal writes the SEO title, description, focus keyword, canonical and social fields through whichever plugin the site runs; yoast_get_post_seo, yoast_update_post_seo and yoast_create_redirect for Yoast; rankmath_meta_get, rankmath_meta_set, rankmath_focus_keyword_set and rankmath_redirects_create for Rank Math; seo_audit_posts for a pass over many posts
• WooCommerce — woo_list_products, woo_create_product, woo_update_product, woo_bulk_set_product_price, woo_bulk_set_product_stock, woo_list_orders, woo_get_order, woo_update_order_status, woo_add_order_note, woo_analytics_overview and woo_analytics_top_products
• Elementor — elementor_build_page and elementor_build_full_page from a brief, section builders such as elementor_add_hero_section, elementor_add_pricing_section and elementor_add_faq_section, and elementor_clear_cache
• Site operations — wp_activate_plugin, wp_check_plugin_updates, wp_clear_all_caches, wp_get_health_tests and the integrations for the plugins a site actually has installed

Connect a site in three steps

MCP Ads talks to WordPress over its REST API, as the WordPress user you connect. That user's role is the ceiling on what the assistant can do: an Editor can write posts but cannot install plugins, an Administrator can do everything.

• Add MCP Ads to your AI client. Paste https://mcp-ads.com/mcp-slim as a custom connector in Claude or ChatGPT, or add it to the MCP config in Cursor, Codex or Gemini CLI, and sign in when the browser opens. There is no API key to copy.
• Connect the site. In wp-admin go to Users → Profile → Application Passwords, create one named "MCP Ads", and enter the site URL, username and that password in the MCP Ads dashboard. The connection is tested against the live site before it is saved.
• If the test is blocked, install the plugin. Download the MCP Ads Connector from https://mcp-ads.com/wordpress-plugin.zip, upload it under Plugins → Add New, activate it, and enter the pairing code from its settings screen in the MCP Ads dashboard. Then ask the assistant something read-only, such as which SEO plugin the site runs.

Sites behind Cloudflare or a security plugin

Cloudflare's managed WordPress rules, and some hosts and security plugins, block /wp-json/ and xmlrpc.php outright, so an API request is refused before WordPress ever checks the password. The MCP Ads Connector answers on admin-ajax.php instead, which those rules leave alone because blocking it breaks most themes. It is not a new API: it takes a REST method and route, hands them to WordPress's own REST router, and returns the result, so every permission check WordPress normally applies still applies. It cannot get past a block on the server's IP address; that has to be allowed at the firewall. Version 1.1.0 and later also opens the Yoast SEO fields to the API. Yoast does not register them itself, so without the plugin WordPress silently drops any change to a Yoast title or description, and MCP Ads tells you so instead of reporting a save that did not happen. Rank Math fields work without it.

What it will not do without you

WordPress is the one platform in MCP Ads where the assistant can change a live website, so the guardrails matter. Every write waits for your approval in the AI client before it runs, and you see the tool name and the arguments first. Ask for a draft when you want to review a post before it goes out; the same tool creates a draft or publishes depending on the status you ask for. Destructive tools such as wp_bulk_delete_posts exist because agencies asked for them, and they run only on an explicit request. A viewer-role user in your MCP Ads workspace can run reads but no writes at all. Setup details and troubleshooting are in the WordPress guide.

Price, licence and the other platforms

MCP Ads is $49/month or $490/year after a 7-day free trial, flat, for every site and account you connect — see pricing. The same connector also carries Search Console, Google Tag Manager, GA4 and the ad platforms, which is useful when a page edit is meant to fix a ranking or a tracking problem. The server is open source under the MIT licence at github.com/RoyAzran/mcp-ads.