The Search Atlas MCP uses credentials issued by the main Search Atlas platform. It does not issue its own authentication system.
There are two supported authentication methods: OAuth (recommended) and API Key (advanced use only). This article explains how each method works, when to use them, and which one you should choose.
🔑 OAuth — Recommended for All Users
OAuth is the recommended and supported authentication method for all customer-facing scenarios.
- Add the MCP endpoint in your MCP-compatible client: https://mcp.searchatlas.com/mcp/
- Start the connection process in your client.
- A browser window opens automatically.
- Sign in to your Search Atlas account.
- Complete the login and approval.
- Return to your client. The connection is now saved, and the client will automatically handle credential storage and refresh going forward.
🔐 What Happens After OAuth Login
Once connected, your client holds the credential and refreshes it automatically — you do not need to log in again for future sessions. All MCP actions will use your Search Atlas account, follow your plan entitlements, and respect your quota limits.
⚙️ API Key — Advanced / Programmatic Use
The MCP also supports authentication using a Search Atlas API key via the X-API-Key header. This method is intended for scripts, server-to-server integrations, and non-interactive environments. Important limitations: there is no browser login flow, no automatic credential refresh, and it requires manual handling of the API key.
⚠️ Which One Should You Use?
If you are a regular user, use OAuth. If you are building automation or backend integrations, use API Key. OAuth is the recommended path for all customer-facing scenarios.
⚠️ Common Issues
- Authentication fails after login — this may happen if your session is expired. Disconnect and reconnect the MCP to refresh credentials.
- Using API Key for normal usage — API keys are not recommended for standard usage. Switch to OAuth for a supported and smoother experience.
OAuth is the standard way to connect MCP because it provides a secure, automatic, and fully supported authentication flow. API keys are available for advanced use cases, but most users should rely on OAuth to ensure a reliable connection and seamless experience.
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.