The hosted WordPress MCP server for AI search.

1. Step 1

   Install the plugin

   Free on WordPress.org. Pair it with a one-time code and tick the permissions you want an agent to have: read, draft, publish, write SEO.

2. Step 2

   Create an API key

   Dashboard → API keys → Generate. One key covers every paired site in your workspace. Revoke it any time.

3. Step 3

   Add the server to your client

   Point your client at https://auditae.app/api/mcp with the key as a Bearer header. Configs for each client are below.

claude mcp add --transport http auditae https://auditae.app/api/mcp \
  --header "Authorization: Bearer ae_live_…"

{
  "mcpServers": {
    "auditae": {
      "url": "https://auditae.app/api/mcp",
      "headers": { "Authorization": "Bearer ae_live_…" }
    }
  }
}

{
  "mcpServers": {
    "auditae": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://auditae.app/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer ae_live_…" }
    }
  }
}

No MCP client? AEBOT in the AuditAE dashboard runs the same tools from a chat box — no config, and it can also run citation audits and push the fixes.

Also on the server: check_brand_citation · get_share_of_voice · explore_llm_mentions · run_technical_audit · discover_brand_entities · validate_schema · generate_schema

• Does WordPress have an MCP server?

  Not built in. WordPress core shipped an MCP adapter for its Abilities API in early 2026 and Automattic maintains a wordpress-mcp plugin; both are self-hosted developer tools that expose the REST API. AuditAE is a hosted alternative: install the free plugin, create a key, and point any MCP client at auditae.app/api/mcp.
• What is a WordPress MCP?

  MCP (Model Context Protocol) is the standard AI clients like Claude, Cursor, and ChatGPT use to call external tools. A WordPress MCP server exposes your site as tools — list posts, update a post, set schema — so an AI agent can read and change the site through a permissioned API instead of a browser.
• Is an MCP WordPress integration safe?

  It is as safe as its permissions. AuditAE gates every call twice (dashboard and plugin) against a capability matrix you set per site, returns previous_state on every write for undo, logs every action, stores the site token encrypted, and never emits its own SEO tags. Start with read + draft, add publish when you trust the workflow.
• How is this different from the WordPress MCP adapter or Automattic's wordpress-mcp?

  Those expose the generic REST or Abilities surface and you run them yourself. AuditAE is remote (no server to host), scoped to AI-search work (SEO meta, schema, llms.txt, citations), aware of Yoast and Rank Math, and returns undo state on every mutation. If you need arbitrary REST access for development, use theirs; if you want an agent to fix SEO across a site, use this.
• Which MCP clients work?

  Claude Code, Cursor, Windsurf, Cline, Zed, and any client that supports Streamable HTTP with an Authorization header. Claude Desktop works through mcp-remote. Claude.ai and ChatGPT web connectors require OAuth, which the endpoint doesn't offer yet — use AEBOT in the AuditAE dashboard for a no-setup chat that runs the same tools.
• Can it bulk-edit posts?

  Yes — that is the point. The tools are per-post, and your client loops: list posts, read the current state, write the change, keep the previous_state. A 40-post meta-description rewrite is 40 writes at 5¢, about $2, and every one is reversible.
• Does it work with Yoast and Rank Math?

  Yes. wp_set_post_seo and wp_set_seo_settings write to whichever SEO plugin is active — focus keyword, title, description, canonical — and only the engines that are active get written. Schema reuses their @ids so the graph stays linked.
• What does it cost?

  The plugin is free and every read tool is free. Writes are 5¢ each, the page composer is 25¢, and citation checks are 5¢ per prompt-engine cell. New accounts get a $5 credit with no card. There is no subscription and no per-site fee.