If your MCP client (such as ChatGPT, Claude, or Cursor) says it cannot connect to the 101domain MCP Server, it usually means there is a problem with the server URL or how your authentication is configured. The 101domain MCP Server expects a specific HTTPS endpoint and a valid 101domain API key passed as a Bearer token.
A small typo in the URL, using the wrong auth type, or mis-formatting the header is often enough to cause a connection failure.
To resolve this
-
Check your MCP client and confirm that it is using HTTPS and is pointing exactly to:
https://mcp.101domain.com/
-
Next, check that the authentication type is set to use a Bearer token and that you are using your 101domain API key as the token value.
-
Finally, if your MCP client requires you to define the HTTP header manually, make sure the Authorization header is formatted exactly as:
Authorization: Bearer [Your_API_Key]
There should be a single space between Bearer and your API key, and no extra characters before or after the key.
-
After updating these settings, save your configuration and try connecting to the 101domain MCP Server again.
For more information on connecting your the 101domain API to your chosen MCP Client, follow out guide 101domain MCP Server Guide.