There is a single canonical connection target and a single authentication model for the Search Atlas MCP. Everything else — which client, which plan, or which namespace — is a variation on these two basics.
This article explains the connection endpoint, the recommended authentication method, and what to check if the connection fails.
🌐 Connection Endpoint
The public MCP endpoint serves the full catalog of Search Atlas tools: https://mcp.searchatlas.com/mcp/
The server also exposes per-product namespaces, for example /mcp/otto/ and /mcp/local-seo-gbp/, but the root endpoint aggregates all namespaces and is what customers should use unless there is a specific reason to scope access. Common tools such as brand vault, knowledge graph, and billing are available in every namespace.
🔐 Authentication
The MCP server validates credentials issued by the main Search Atlas platform. It does not issue its own credentials. OAuth is the recommended and supported path for all customer-facing scenarios.
The server also accepts a Search Atlas API key via the X-API-Key header, but that path exists for scripts and server-to-server integrations where an interactive browser login is not possible. It is not recommended for regular customer use. If a customer asks which to use, steer them to OAuth.
⚙️ Connect MCP
- Use the main endpoint: https://mcp.searchatlas.com/mcp/
- Add that endpoint in your MCP-compatible client, such as Claude Desktop, Claude.ai, Cursor, or ChatGPT connectors.
- When the client starts the connection flow, complete the one-time Search Atlas login in the browser. This is the OAuth flow recommended and supported for customer-facing scenarios.
- After you sign in, the client holds and refreshes the credential automatically. From that point forward, the MCP connection remains saved in the client.
⚠️ If the Connection Fails
The three most common causes, in order:
- You are not already logged into Search Atlas when the browser window opens. Sign in to dashboard.searchatlas.com first, then try again.
- Your plan does not include MCP access. Check your plan entitlements — MCP access is controlled at the plan level.
- Your session is stale or expired. Disconnect the MCP in your client and reconnect to trigger a fresh login.
To connect MCP successfully, use the root Search Atlas endpoint and the OAuth login flow. Once connected, your client can access the Search Atlas tool catalog available under your account, subject to your plan entitlements and quota rules.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.