Start here
Connect Claude, ChatGPT, Codex, VS Code or Cursor to AuditAE (MCP)
Connect Claude, ChatGPT, Claude Code, Codex, VS Code or Cursor to AuditAE's MCP server: sign in or use an API key. No-account agents use /api/mcp/pay.
On this page· 12 sections
Sign-in connects your personal workspace. Team workspaces use an API key.
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. Claude and VS Code also install from a link in Client setup.
2. Choose OAuth or an API key
Claude, ChatGPT, Claude Code, Codex and VS Code sign in (OAuth): add the server and sign in with your AuditAE account when the client asks. No key to copy; the connection uses your personal workspace and its balance.
Cursor, Windsurf, team workspaces and most other clients use an API key: the same ae_live_… Bearer key as the REST API. Sign-in always connects your personal workspace, so a team workspace connects with a key, from Claude Code, Codex, VS Code, Cursor, Windsurf or Claude Desktop's config file. 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.
An agent with no AuditAE account: connect to https://auditae.app/api/mcp/pay with no credentials. The free tools run straight away, and add_site creates a workspace and returns its key. See Agents without an account.
3. Add the server to your client
Use the button, command or config block for your client from Client setup below. Clients that sign in open your browser the first time they connect. Config-file clients may need a reload after you save, and Claude Desktop a restart.
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
Opens Claude's Add custom connector dialog with AuditAE filled in. Confirm, then sign in to AuditAE or create a free account in the same step. The connector works in Claude on the web, in Claude Desktop and in Cowork.
Add AuditAE to Claude. Team or Enterprise Owner? Add it for your organization.
Server URL
https://auditae.app/api/mcp
- Claude Free allows one custom connector.
- On Team and Enterprise plans only Owners add custom connectors, from Organization settings → Connectors. Members then connect it from Customize → Connectors.
ChatGPT
ChatGPT adds custom MCP servers as plugins. Four steps; the last one signs you in.
- Open chatgpt.com/plugins, select +, then Add custom MCP server. If you don't see that option, turn on developer mode in ChatGPT's settings (on Business, Enterprise and Edu workspaces an admin does this).
- Name it AuditAE, paste
https://auditae.app/api/mcpas the server URL and choose OAuth for authentication. - Select I understand and want to continue, then Create as a plugin.
- Install the plugin and sign in to AuditAE when ChatGPT asks.
Server URL
https://auditae.app/api/mcp
- Needs a plan that allows custom MCP servers. Check your plan and workspace settings.
- When AuditAE adds tools, open AuditAE at chatgpt.com/plugins and select Refresh.
Claude Code
Run this once in your terminal; --scope user adds AuditAE to every project. Then run /mcp in Claude Code, pick auditae and choose Authenticate to sign in.
Terminal
claude mcp add --transport http --scope user auditae "https://auditae.app/api/mcp"
Team workspace? Sign-in connects your personal workspace. To connect a team workspace, switch to the team in AuditAE and follow this client's key setup under API keys.
Codex
One command for the Codex CLI. It detects AuditAE's sign-in and opens your browser; if it doesn't, run codex mcp login auditae. The Codex IDE extension and the ChatGPT desktop app read the same ~/.codex/config.toml: you can paste the block instead, then run codex mcp login auditae (or sign in from the app's MCP settings).
Terminal
codex mcp add auditae --url "https://auditae.app/api/mcp"
~/.codex/config.toml
[mcp_servers.auditae]
url = "https://auditae.app/api/mcp"
tool_timeout_sec = 300
Team workspace? Sign-in connects your personal workspace. To connect a team workspace, switch to the team in AuditAE and follow this client's key setup under API keys.
- tool_timeout_sec = 300 gives long citation runs room to finish; Codex's default is 60 seconds.
VS Code
Opens VS Code's install prompt for AuditAE, for GitHub Copilot agent mode. Select Install, then sign in when VS Code asks. Or run MCP: Open User Configuration and add the block below.
Install in VS Code or VS Code Insiders.
mcp.json (user configuration)
{
"servers": {
"auditae": {
"type": "http",
"url": "https://auditae.app/api/mcp"
}
}
}
Team workspace? Sign-in connects your personal workspace. To connect a team workspace, switch to the team in AuditAE and follow this client's key setup under API keys.
- VS Code caps the tools one request can use (128 at last check), counting its built-in tools and your other servers. If it warns, turn off tools you don't need in the tool picker.
Cursor
Cursor connects with an API key for now. Add this to ~/.cursor/mcp.json, your user config, so the key never sits in a project folder, and replace ae_live_… with your key.
Create a key at API keys (a free account is enough).
~/.cursor/mcp.json
{
"mcpServers": {
"auditae": {
"url": "https://auditae.app/api/mcp",
"headers": {
"Authorization": "Bearer ae_live_…"
}
}
}
}
- Sign-in and a one-click install for Cursor aren't available yet, so it needs a key.
- If the tools don't show up, reload Cursor after saving the file.
Windsurf
Windsurf (Devin Desktop) connects with an API key. Add this to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows; older Windsurf builds read ~/.codeium/windsurf/mcp_config.json) and replace ae_live_… with your key.
Create a key at API keys (a free account is enough).
mcp_config.json
{
"mcpServers": {
"auditae": {
"serverUrl": "https://auditae.app/api/mcp",
"headers": {
"Authorization": "Bearer ae_live_…"
}
}
}
}
- Cascade allows 100 tools across all your MCP servers, and AuditAE's full set uses most of them. Turn off servers you aren't using.
- The config path has moved between versions; check your version's MCP settings if neither file is read.
Other clients
Most other clients that speak remote MCP over Streamable HTTP, such as Zed, Cline, Continue, Kiro, Goose or JetBrains, connect to the URL. Clients that support OAuth client metadata documents sign in; the rest send an API key in the Authorization header.
Create a key at API keys (a free account is enough).
Server URL
https://auditae.app/api/mcp
URL and key header
URL: https://auditae.app/api/mcp
Header: Authorization: Bearer ae_live_…
- Clients that only launch local (stdio) servers bridge to the hosted endpoint with mcp-remote: see Claude Desktop for the config.
Claude Desktop
Claude Desktop uses the Claude connector from your Claude account, so you don't need this if you added it there. To connect a team workspace with a key instead, bridge to the hosted endpoint with mcp-remote (Desktop's config file only launches local stdio servers): add this to claude_desktop_config.json, replace ae_live_… with your key, and restart the app.
{
"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, ChatGPT, Claude Code, Codex, VS Code and other clients that support OAuth client metadata documents) 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. Cursor and Windsurf connect with a key for now. Create, rotate and revoke keys at API keys. - Keys stay out of commands and projects: the key setup on API keys reads
$AUDITAE_API_KEYfrom a hidden prompt, so the key never lands in your shell history. Keep config files that hold a key in your user folder, not a project folder you might commit. - 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.
If a client stops connecting
- Sign-in expired: a 401 with
error="invalid_token"means the client sent a sign-in that's no longer valid. Disconnect and reconnect the server, or in the Codex CLI runcodex mcp login auditae. - Key refused: a 401 that says the key is invalid means it was revoked, rotated or mistyped. Make a new one at API keys and update your client.
- Codex with a key: Codex reads
$AUDITAE_API_KEYwhen it starts, so restart it after changing the key.
What the tools do
Every client gets the same server: 99 tools across nine families:
- Citation & mentions (15):
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_citation_sources(the pages engines cite where you lose — "best X" listicles, directories, review sites, forum threads, news, competitors' pages — as outreach targets, each checked for whether it already names or links you, ranked by how many lost answers cite it, with the next step: pitch the author, submit the listing, collect reviews, answer the thread — $0.10 per site per day),find_content_gap,extract_competitors_from_text(analyze AI output you already have — bundled), andget_audit(an existing audit's per-prompt × engine results — who got cited, which URLs, and the top actions of the playbook the audit already paid for — 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 markedalready_doneand copy the site doesn't back up comes back as adraftto confirm — $0.50), plusschedule_recheck,get_recheckandcancel_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),monitor_citations(re-ask a site's questions every week or month and email the owner when a citation is gained or lost — free to set up, each run billed per check) andget_changes(opens with the site's weekly briefing when it has one — what moved this week and up to 5 priced fixes — then what gained or lost a citation since the previous run, who's cited instead, and tracked keywords that moved in Google — free). - Technical & site health (13):
run_technical_audit(one page — the homepage by default — plus Core Web Vitals, answers in about 10s with Core Web Vitals usually on one free repeat call — 3 pages a day free, then 2¢/page),crawl_site(whole-site Site Audit, up to 10,000 pages: 174 checks graded error, warning or notice, Site Health and 9 theme scores, 1¢ per 10 pages with link checks and Core Web Vitals included; big sites keep crawling in the background; optional settings narrow it to the sitemaps, one sitemap or a URL list, include / exclude paths, ignore query parameters, add subdomains, obey one bot's robots.txt group, crawl as mobile or politely, and leave checks out of the scores),get_latest_crawl(reads the latest or an older crawl, filtered by theme, severity or check — free),get_crawl_issue(one check's rule, why, fix and affected URLs with evidence, or only those new or fixed since the previous crawl — free),compare_crawls(what changed between two crawls: Site Health, new and fixed issues per check, pages added or removed — free),schedule_crawl(weekly or monthly re-crawls with a summary email — free to set up, each run 1¢ per 10 pages when it runs),optimize_image(resizes and compresses images to WebP, or keeps their format, and returns 48-hour download links: a crawl's images over 200 KB, largest first, or any public image URL — 1¢ per 5 images optimized, free when an image barely shrinks),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),check_ai_crawlers(which AI crawlers robots.txt and the firewall let in, with robots.txt fixes — free) andcheck_llms_txt(validates /llms.txt — free). - WordPress (28): 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, SEO meta in Yoast, Rank Math, or AuditAE's own fields on a site with no SEO plugin (plugin 0.37.0+) (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), the Page Composer (wp_read_page_blocks, free;wp_design_pageat 25¢), and in-place image compression (wp_optimize_media: each Media Library file keeps its name and URL, thumbnails included, originals backed up; 5¢ per call plus 1¢ per 5 images replaced;wp_restore_mediaundoes it, free; plugin 0.35.0+). Standard WP mutations cost 5¢ each, billed per write; reads are free. Every wp_* tool takes either thewp_list_sitesid or the site'slist_sitessite_id, and schema writes are validated before they reach the site. What each tool needs from the plugin: WordPress permissions. - WordPress SEO (17): the plugin's own SEO data on a paired site — the AI crawler log (
wp_list_crawler_hits: which AI bots fetched which pages, and what status they got), 404 → 301 redirects (wp_list_redirects,wp_suggest_redirects_from_404sfor the URLs AI bots hit that 404,wp_add_redirect,wp_delete_redirect), internal links (wp_get_link_graphfor orphan pages,wp_get_post_linksfor one page's links and ready-made suggestions,wp_insert_internal_linkto link one phrase), broken internal links (wp_list_broken_links,wp_fix_broken_linkto point one at a working page or unlink it; plugin 0.38.0+), the robots.txt audit (wp_get_robots_audit: which AI crawlers the site blocks) and Media Library metadata (wp_list_mediawith a missing-alt filter,wp_get_media,wp_update_mediafor alt text, title, caption and description,wp_bulk_update_media_altfor up to 50 alt texts at once, billed per image changed,wp_rename_mediafor descriptive file names, with the old URLs rewritten in content) and image imports (wp_upload_media: AuditAE downloads the image from a public URL, checks it's a real JPEG, PNG, GIF, WebP or AVIF up to 15 MB, and hands WordPress a short-lived private copy, so the site never fetches the URL itself; the same image sent again returns the attachment already made, free). Reads are free; each write is 5¢, only when it changes something, and returns the previous state for undo (an upload says how to delete it in wp-admin). Redirects and media metadata writes need the Write SEO permission; an image import needs draft; a link insert or broken-link fix needs draft, or publish on a live post. - Account (9):
record_change(add an edit to the site's change history, free),list_sites(every site with its site_id, competitor domains, latest audit and whether Search Console and GA4 are connected — call it first),add_site(add a website from the chat, or add competitor domains to one already added; in a workspace that has never run an audit it also starts the starter audit, paid from the workspace's credit),get_site_briefandupdate_site_brief(the site's brief — brand, customers, competitors, keywords, strategy — shared with AEBOT and every connected AI client, so the next session starts from it; see Memory),get_balance,create_top_up_link— see Top-ups for agents, plusget_client_portalandupdate_client_portalto share a site's read-only client page and get its link. Free. - Google data (5):
query_search_console(clicks, impressions, CTR and position by query, page, country, device or date) andquery_google_analytics(any GA4 dimensions and metrics) andget_ai_referral_traffic(visits from ChatGPT, Perplexity, Claude, Gemini and Copilot, with the change against the previous period and their landing pages) andinspect_url(Search Console's URL Inspection for one page, or up to 20 in one call: indexed or not and why, last crawl, Google's canonical, and the rich results Google detected — the check that a fix you published is indexed and its schema is picked up). They use the Google connection and the GA4 property / Search Console site picked in each site's Settings (a Search Console property that exactly matches the site is linked automatically), so there's no Google Cloud project to set up. The two report tools cost 1¢ per 100 rows returned, rounded up, with a 1¢ minimum per call (a 1,000-row Search Console pull is 10¢, a 25-row one 1¢);inspect_urlis 1¢ per URL inspected andget_ai_referral_traffic1¢ per call; a call that errors is free, and the dashboard and AEBOT read the same data free.find_search_opportunitiesdoes the analysis in one call: it reads the last 28 days of Search Console (page × query), the 28 days before and the same days a year earlier, GA4 organic revenue per landing page and Google keyword data for the top queries, and ranks the pages worth working on by the clicks and revenue each could win — CTR gaps, striking-distance queries (4–20), pages losing clicks, pages splitting a query, AI Overview losses and pages that dropped out of the index — each with its next step ($0.15 per site per day; repeats, filters and more results that day are free). See Connect Google. - Keyword research & rank tracking (4):
keyword_research(related keywords for a seed term with volume, CPC, difficulty and intent, in the chosen country — $0.25 per run of 25+ keywords, pro rata below that, free under 10),track_keywords(up to 20 keywords per call: a live Google check now — position, ranking URL, AI Overview presence and citation, search volume — then a weekly re-check, $0.05 per keyword per check),list_tracked_keywords(latest positions and changes — free) anduntrack_keyword(stops the weekly checks — free).query_search_consolesuggests queries worth tracking: the ones already ranking 4–20 that the site doesn't track yet. - SEO data for any keyword or domain (5):
get_serp(live Google top 10–30 with AI Overview sources, featured snippet and People Also Ask — $0.05),get_domain_keywords(the keywords any domain ranks for, by traffic, with its totals — $0.10),get_competing_domains(its organic competitors and shared keywords — $0.10) andget_keyword_metrics(volume, 12-month trend, CPC, difficulty and intent for up to 60 keywords — $0.10). Per call, no subscription; the same call within 24h is free, and on the no-account endpoint one data call a day is a free sample. - Schema (3):
discover_brand_entities(the brand's Wikidata identifiers for sameAs, plus its Google Knowledge Graph entity, matched by domain or Wikidata id, never by name),generate_schema,validate_schema— the same schema-autopilot tools AEBOT uses (see Using AEBOT).
What you changed, and what happened next
AuditAE keeps a record of the edits to a site. WordPress edits made through the wp_* tools, AEBOT or the dashboard record themselves once the page is live, and so do URLs sent with submit_urls. An agent editing a site's code or another CMS calls record_change (free) with the changed URLs and a one-line summary.
About 2 and 4 weeks later, AuditAE reads Search Console for that page and for the whole site over the same days, and get_changes reports both under your_changes. Each result says what happened to the page, and it's judged on clicks when there are enough, otherwise on rank. It says so when there's too little data to judge or when another change hit the page in the same days. A result shows what happened after a change, not proof the change caused it. Results are free and need Search Console connected.
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. Free results, and the Google data tools' results, end with suggested_next: one next call computed from that result (tool, args, price_cents, price_label and why), such as tracking the queries Search Console shows ranking 4–20 or crawling the whole site after a one-page audit, so your agent can offer it with its price and run it only if you agree. 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,check_ai_crawlers,check_llms_txt,check_citation_free. Limited to 30 free calls per IP address a day, with a site-wide daily ceiling. - One free citation check a day:
check_citation_freeasks one buyer question of ChatGPT, Perplexity, Gemini and Google AI Overviews and returns who's cited, with a shareable report — the same check as the free one on the website, one fresh run per IP address a day. - Pay per call. Paid tools answer with a Machine Payments Protocol (MPP) payment challenge for the call's price. The agent pays by card (minimum $0.50; anything above the call's price stays as credit) and retries with the credential. The first paid call, or
add_site, creates an agent workspace and returns its API key: send it as a Bearer token on later calls to spend leftover credit and reuse sites and reports. - Hand the workspace to a person.
create_top_up_linkalso returns aclaim_url. A person who opens it and signs up (free, no card) gets the agent workspace's sites, reports, monitors and API key in their new account; leftover credit carries over. They choose whether the agent's key keeps working there, drawing on their balance, or is turned off. Signing in to an existing account works too (no extra credit). The link works once and expires after 14 days. - With a workspace:
list_sitesshows its sites,get_auditreads results for free,submit_urlspings IndexNow for free,get_changessays what moved since the last run for free, andschedule_recheckandmonitor_citations(need a funded workspace) re-ask questions later or every week. - WordPress tools need an account and a paired plugin: Pair the AuditAE WordPress plugin.
Pay per call over HTTP
Agents that make plain HTTP requests rather than MCP calls can pay per request, with no account and no key. POST a JSON body to a resource with no credentials and it answers 402 Payment Required with a Machine Payments Protocol challenge in the WWW-Authenticate header (Payment … method="stripe" intent="charge"). Pay it by card with a Stripe shared payment token (for example npx @stripe/link-cli mpp pay) and send the same request again with the credential in Authorization: Payment …. The paid response carries a Payment-Receipt header, the result, and the API key of a new agent workspace holding whatever the call didn't spend, usable on https://auditae.app/api/mcp/pay.
-
POST /api/mpp/domain-keywords: Keywords any domain ranks for in Google, the same call asget_domain_keywords($0.10). $0.50 per request, Stripe's card minimum: the other $0.40 stays as credit in the new workspace. Body:{"domain":"linear.app","limit":10}. -
Nothing is charged for a request that can't run: a body that doesn't validate gets a 400 before any challenge.
-
Limits: 60 requests a minute per IP address.
-
Discovery: /api/mpp/openapi.json, an OpenAPI 3.1 document with
x-payment-infoon each resource. Validate the server withnpx mppx validate https://auditae.app/api/mpp. -
Paying means agreeing to the Terms of Service and Privacy Policy; the challenge links both.
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.
- Search Console MCP: asking your Search Console data which queries and pages are slipping and whether a page is indexed, then fixing it from chat.
- Google Analytics MCP: asking your GA4 data questions from chat, including AI-assistant referrals.
Try it in AuditAE
Create an API keyRelated docs
- Apply a fix plan and check it workedTurn an audit into exact edits, apply them on WordPress or any other site, ping the crawlers, and re-check whether AI engines now cite you.
- Credits, prices and top-upsWhat each AuditAE action costs, how to top up (in the app, in AEBOT chat or from an agent), how auto-refill works, and what happens when credit runs out.
- Pair the AuditAE WordPress pluginInstall the free AuditAE plugin, pair it with an 8-character code, and choose what AEBOT may change. Plus fixes for pairing errors and llms.txt 404s.
- REST API and API keysRun AuditAE from your own code with an API key and the same credit balance as the dashboard. Endpoints, prices, 402 top-ups and rate limits.
- Site Audit: crawl a site and read Site HealthCrawl up to 10,000 pages for 1¢ per 10 pages and get Site Health, 9 theme scores and 174 checks, each with why it matters and how to fix it.
Still stuck? Signed in, ask AEBOT in Documentation mode (free). Or email support@auditae.app.