Connect SearchChamp to your AI apps.

Audit card

A scored summary of your latest site audit — top issues, severity, and what changed since the last run — rendered inline as you chat.

Opportunities board

Your ranked opportunity queue, grouped by source and effort, so you can triage and queue the next fix without leaving the conversation.

Rank movers

The keywords that moved the most since your last check — up and down — with the page and the likely cause.

AI visibility report

Citation presence and sentiment across the AI engines you track, summarized for the site and date range you ask about.

Brief preview

A generated content brief — outline, target keywords, and sourcing notes — ready to hand off or pull into your own editor.

Claude Desktop

Add this to claude_desktop_config.json — ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows — then restart Claude Desktop. That file only accepts local (stdio) servers, so the token reaches us through mcp-remote, a third-party bridge run on demand via npx. Prefer signing in instead? Add SearchChamp as a custom connector — see Connect Claude. Both paths reach the same SearchChamp workspace; the connector adds interactive cards and a sign-in flow on top of what the token config below gives you.

{
  "mcpServers": {
    "searchchamp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-dev.searchchamp.dev/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer atl_mcp_your_token_here"
      }
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json (or your project’s .cursor/mcp.json), then reload Cursor’s MCP settings. Cursor connects to the remote URL directly — no bridge needed — and its schema takes no type field. Cursor doesn’t support custom OAuth connectors the way Claude and ChatGPT do, so the token path is the only way to connect it today.

{
  "mcpServers": {
    "searchchamp": {
      "url": "https://mcp-dev.searchchamp.dev/mcp",
      "headers": {
        "Authorization": "Bearer atl_mcp_your_token_here"
      }
    }
  }
}

Codex CLI

Put the token in SEARCHCHAMP_MCP_TOKEN in the shell that launches Codex, then run this command. Codex stores only the environment-variable name — the token is not placed in command arguments or committed configuration. The token path uses its minted read/full and optional site lock; the OAuth connector instead follows your interactive account grant.

codex mcp add searchchamp --url https://mcp-dev.searchchamp.dev/mcp --bearer-token-env-var SEARCHCHAMP_MCP_TOKEN

Claude Code, VS Code & other MCP clients

The standard streamable-HTTP shape — drop it into Claude Code’s .mcp.json (or ~/.claude.json for every project), VS Code’s MCP settings, or any client that reads an mcpServers block. These clients require "type": "http" alongside the URL; a few — Cursor above among them — leave it out. If your client rejects the entry, that key is the first thing to add or drop. This is the shape most newer MCP clients expect by default, so if you’re integrating a tool not listed here, start from this config rather than the Claude Desktop or Cursor variants above.

{
  "mcpServers": {
    "searchchamp": {
      "type": "http",
      "url": "https://mcp-dev.searchchamp.dev/mcp",
      "headers": {
        "Authorization": "Bearer atl_mcp_your_token_here"
      }
    }
  }
}