The hosted WordPress MCP server for AI search.

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.

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.
• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”

ChatGPT adds custom MCP servers as plugins. Four steps; the last one signs you in.

1. 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).
2. Name it AuditAE, paste https://auditae.app/api/mcp as the server URL and choose OAuth for authentication.
3. Select I understand and want to continue, then Create as a plugin.
4. Install the plugin and sign in to AuditAE when ChatGPT asks.

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.
• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”

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.

claude mcp add --transport http --scope user auditae "https://auditae.app/api/mcp"

• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”

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).

codex mcp add auditae --url "https://auditae.app/api/mcp"

[mcp_servers.auditae]
url = "https://auditae.app/api/mcp"
tool_timeout_sec = 300

• tool_timeout_sec = 300 gives long citation runs room to finish; Codex's default is 60 seconds.
• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”

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.

On a phone? Copy this page link and open it on the computer where VS Code is installed, or add the block below there with MCP: Open User Configuration.

{
  "servers": {
    "auditae": {
      "type": "http",
      "url": "https://auditae.app/api/mcp"
    }
  }
}

• 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.
• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”

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.

{
  "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.

Then ask “What's my AuditAE balance and what can you do?”

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.

{
  "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.

Then ask “What's my AuditAE balance and what can you do?”

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.

https://auditae.app/api/mcp

URL:    https://auditae.app/api/mcp
Header: 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_…" }
    }
  }
}

• Clients that only launch local (stdio) servers can bridge to the hosted endpoint with mcp-remote, as in the last block.
• Sign-in connects your personal workspace. Team workspaces use an API key.

Then ask “What's my AuditAE balance and what can you do?”