Connect Claude, ChatGPT or Cursor to AuditAE (MCP)

Steps

1. Copy the server URL

AuditAE ships a remote MCP endpoint (Streamable HTTP, stateless) at https://auditae.app/api/mcp. There's no AuditAE package to install: every client connects to that URL.

2. Choose OAuth or an API key

Claude.ai, ChatGPT and other OAuth clients: add the endpoint URL as a custom connector and sign in with your AuditAE account when prompted. No key to copy; the connection uses your personal workspace and its balance.

Claude Code, Cursor, Windsurf and other config-file clients: pass the same ae_live_… Bearer key as the REST API (team workspaces use this path). Create one at API keys: click Create key and copy the key from the banner straight away. It's shown once; lose it and you'll need to Rotate it.

3. Add the server to your client

Paste the URL, command or config block for your client from Client setup below. Claude Desktop needs a restart after you save its config.

4. Try a first prompt

Ask: "List my AuditAE sites, read the latest audit for my site, then get a fix plan for it." The agent calls list_sites (free) for site ids and the latest audit, get_audit (free) for who got cited on each prompt and engine, then get_fix_plan ($0.50) for the exact edits. See Apply a fix plan and check it worked for the rest of the loop.

Client setup

Every client gets the same server and the same tools. Pick yours:

Claude.ai and ChatGPT

Custom connector, signed in with OAuth. Add the server URL as a custom connector and sign in with your AuditAE account. No API key and no config file: the connection covers every paired site in your workspace.

https://auditae.app/api/mcp

Claude Code

One command in your terminal. Adds the server to your project or user scope. Run it once, then ask Claude Code to list your WordPress sites to confirm the connection.

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

Cursor · Windsurf · any HTTP client

Add this to .cursor/mcp.json, or your client's MCP config. Streamable HTTP with an Authorization header. The same block works in Windsurf, Cline, Zed, and any client that speaks remote MCP with custom headers.

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

Claude Desktop

Add this to claude_desktop_config.json. Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint. Restart the app after saving.

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

OAuth or API key

• OAuth (Claude.ai, ChatGPT and other connector clients) signs you in as a person and always uses your personal workspace and its balance. Team workspaces use an API key instead.
• API keys (ae_live_…) belong to a workspace, personal or team, and work for the MCP server and the REST API. Create, rotate and revoke them at API keys.
• Rate limits: 60 requests a minute per key, and 30 failed sign-ins a minute per IP address.
• New tools: clients load the tool list when they connect. If a tool you expect is missing, disconnect and reconnect the server.

What the tools do

Every client gets the same server: 56 tools across six families:

• Citation & mentions (12): check_brand_citation (one prompt across N engines), get_share_of_voice (full matrix with domain-level cite counts), explore_llm_mentions (historical AI-citation corpus), explore_web_mentions (open-web brand mentions with sentiment, $0.25), mine_competitor_prompts (prompts where a competitor earned the citation — one competitor, or all of them in one run), find_content_gap, extract_competitors_from_text (analyze AI output you already have — bundled), and get_audit (an existing audit's per-prompt × engine results — who got cited, which URLs — free), get_fix_plan (the exact edits that get you cited, written for the site's platform, checked against the live site so fixes already in place come back marked already_done and copy the site doesn't back up comes back as a draft to confirm — $0.50), plus schedule_recheck, get_recheck and cancel_recheck (re-ask a plan's prompts N days after you publish and compare citations before vs after — free to schedule, each check billed when it runs).
• Technical & site health (7): run_technical_audit (homepage crawl + Core Web Vitals, answers within ~25s — free), crawl_site (multi-page crawl, $0.01/page), get_latest_crawl (cached result — free), detect_tech_stack (CMS / platform detection — free), check_agent_readiness (can AI agents reach, read and buy from the site — free), get_backlink_summary (off-page authority for the site or a competitor — free), submit_urls (ping IndexNow — Bing, Yandex and others — with changed URLs from AuditAE's server — free).
• WordPress (26): read/write tools that pair with the free AuditAE WordPress plugin — wp_list_sites, wp_site_status, wp_list_posts, wp_get_post, wp_create_post, wp_update_post, Yoast/Rank Math meta (wp_get_post_seo, wp_set_post_seo, wp_get_seo_settings, wp_set_seo_settings), FAQ, post-level, and organization-level JSON-LD CRUD, schema probe, llms.txt curation (wp_get_llms_txt, wp_set_llms_txt, wp_reset_llms_txt), and the Page Composer (wp_read_page_blocks, free; wp_design_page at 25¢). Standard WP mutations cost 5¢ each, billed per write; reads are free. Every wp_* tool takes either the wp_list_sites id or the site's list_sites site_id, and schema writes are validated before they reach the site. What each tool needs from the plugin: WordPress permissions.
• Account (6): list_sites (every site with its site_id, competitor domains and latest audit — call it first), get_balance, create_top_up_link, and on the remote server pay_with_shared_payment_token — see Top-ups for agents, plus get_client_portal and update_client_portal to share a site's read-only client page and get its link. Free.
• Google data (2): query_search_console (clicks, impressions, CTR and position by query, page, country, device or date) and query_google_analytics (any GA4 dimensions and metrics). They use the Google connection and the GA4 property / Search Console site picked in each site's Settings, so there's no Google Cloud project to set up. Free. See Connect Google.
• Schema (3): discover_brand_entities (Wikidata-backed identifier lookup), generate_schema, validate_schema — the same schema-autopilot tools AEBOT uses (see Using AEBOT).

Any website, not just WordPress

get_fix_plan detects what the site is built on and returns each fix with steps for that platform plus paste-ready JSON-LD and meta tags. On a paired WordPress site the agent applies it with the wp_* tools; on a code-built site (Next.js, Astro, …) a coding agent like Claude Code or Cursor edits the repo; on Shopify, Webflow, Wix, Squarespace or Framer it walks you through the editor.

Prices

MCP calls spend the same credit balance as the dashboard: 5–12¢ per check depending on the engine (Perplexity 5¢, ChatGPT 7¢, Google AI Overviews 9¢, Gemini 12¢). Each tool's description includes its price (a Billing: line), so your agent can quote it before calling. When the balance hits zero, in-flight audits return partial: true with the cells that did run. Full list, top-ups and limits: Credits, prices and top-ups.

Agents without an account

A separate endpoint, https://auditae.app/api/mcp/pay, serves agents that have no AuditAE account. It takes no OAuth; an ae_live_… key is optional.

• Free with no credentials: extract_competitors_from_text, discover_brand_entities, validate_schema, generate_schema, run_technical_audit, check_agent_readiness. Limited to 30 free calls per IP address a day, with a site-wide daily ceiling.
• Paid tools need a funded workspace. Pay-per-call isn't switched on yet. Call add_site (free) to get a workspace API key, then create_top_up_link (free) and have a person pay the link ($5 minimum), then retry with the key as a Bearer token. Or sign up and use https://auditae.app/api/mcp with OAuth or a key.
• With a workspace: list_sites shows its sites, get_audit reads results for free, submit_urls pings IndexNow for free, and schedule_recheck (needs a funded workspace) re-asks a plan's prompts later.
• WordPress tools need an account and a paired plugin: Pair the AuditAE WordPress plugin.

Machine-readable discovery

• MCP server card: /.well-known/mcp/server-card.json, with every tool, its price and the no-account endpoint.
• /llms.txt: a summary of AuditAE for language models.
• /openapi.json: the REST API as OpenAPI 3.1. See REST API and API keys.

More guides

• AuditAE MCP server guide: what an MCP server is, connecting each client, and what a real run returns.
• WordPress MCP: editing WordPress from Claude, ChatGPT or Cursor.
• Google Analytics MCP: asking your GA4 and Search Console data questions from chat.