SearchChampMCP overview
Connect an AI client to SearchChamp data and tools over the Model Context Protocol.
SearchChamp's hosted MCP server lets compatible AI clients read your SEO data and, with explicit scopes, drive approved workflows. The client chooses a tool from SearchChamp's published catalog; SearchChamp validates the credential, organization, site, plan, scope, arguments, and usage guard before running it.
Transport endpoints
SearchChamp implements stateless Streamable HTTP. Every request is independent; clients do not need to preserve an MCP session ID.
| Environment | MCP endpoint |
|---|---|
| Production | https://mcp.searchchamp.com/mcp |
| SearchChamp development/testing | https://mcp-dev.searchchamp.dev/mcp |
OAuth discovery is available from the same host at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. Supported OAuth features are authorization code, refresh token, PKCE S256, dynamic client registration, and RFC 8707 resource indicators.
Choose an authentication path
| Path | Best for | Identity and catalog |
|---|---|---|
| OAuth connector | Claude and ChatGPT custom connectors | Sign in as a SearchChamp user, choose one organization, and receive the full 38-tool catalog. Each call is still limited by the granted OAuth scopes and your site access/role. OAuth access is currently allow-listed through the MCP beta. |
| User-generated MCP token | Cursor, Codex CLI, Claude Code, VS Code, automation, and clients without custom OAuth connectors | Create an atl_mcp_... bearer under Settings → MCP Tokens. The token is organization-scoped or locked to one site and receives a curated plan-dependent catalog. |
API keys are not MCP tokens
An atl_... API key authenticates the REST API. An atl_mcp_... token authenticates the MCP endpoint. They are not interchangeable.
What is available
- Site discovery, daily briefs, site snapshots, rank movements, AI Visibility, opportunities, audits, backlinks, tracked keywords, and bot-access reports.
- Draft-content, brand-voice, page-recommendation, custom-site publication, Page Optimizer, and llms.txt workflows.
- Audited action approval/decline and publishing tools on appropriately scoped OAuth connections.
- Natural-language
ask_atlio, which answers from the same grounded path used in the SearchChamp app and proposes rather than silently runs credit-spending work.
See the complete tool catalog before granting a scope or automating a workflow.
Permissions at a glance
| Scope | Allows |
|---|---|
mcp:read | Read tools and ask_atlio. |
mcp:approve | Read plus configuration decisions such as approving/declining an action. |
mcp:spend | Read plus spend-class tools such as generate_llms_txt. |
mcp:act | Every class: read, approve, spend, mutate-site, and publish-live. |
Scopes are additive by grant. A tool checks its required class before running. A tool can also require an editor/owner role, a supported plan, a connected CMS, or a product-specific enablement switch.
Read next
- Connect clients — OAuth setup and every supported token configuration shape.
- MCP tool reference — every tool, parameter, return, scope, credit cost, and token availability.
- Workflows, security, and troubleshooting — example prompts/calls, limits, revocation, and error recovery.