The Search Atlas MCP (Model Context Protocol) endpoint allows external AI agents and tools to connect with your Search Atlas account. If you are seeing timeout errors, DNS resolution failures, or MCP initialization issues, this article explains what to have ready when escalating to our support team so we can investigate and resolve the issue on the backend as quickly as possible.
DNS resolution failure: Your client cannot resolve the MCP endpoint domain
Connection timeout: The MCP endpoint does not respond within the expected window
Initialization error: The MCP handshake starts but fails before tools are loaded
API or server errors: Requests via MCP return error responses
Tool list empty or missing: Connected successfully but no tools appear
MCP endpoint connectivity and initialization failures are typically caused by backend configuration issues that require investigation by our team. To help us resolve your case efficiently, please gather the following before reaching out via the chat widget:
Your Search Atlas account email or username
The exact error message you are seeing — copy it in full, including any error codes
The timestamp of when the failure first occurred or was most recently observed (include your timezone)
A description of your MCP client setup — for example, which AI agent or tool you are using to connect
Steps you have already tried — such as re-entering your API key, restarting your client, or checking your network connection
Whether the issue is consistent or intermittent — and if intermittent, how often it occurs
Having this information ready will allow our team to investigate your specific account and endpoint configuration on the backend without unnecessary back-and-forth.
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.