MCP Not Responding

Check the MCP Endpoint

If your AI tool reports that the MCP server is not responding, the first step is to verify that the endpoint is reachable. Try opening your MCP URL in a web browser — you should see a response from the server (even if it is an error page, that means the server is running).

If you get nothing at all, the server may be down. Check our status page for any known outages.

Verify Your Configuration

Go through your MCP configuration and make sure:

• The endpoint URL is complete and correct, including https://.
• Your API key is set in the right field.
• There are no typos or extra characters in the URL or key.
• You saved the configuration and restarted the AI tool.

Common Misconfigurations

Here are the most common configuration mistakes we see:

1. Missing /api/mcp path — The URL must end with /api/mcp, not just the domain.
2. HTTP instead of HTTPS — Make sure you are using https://.
3. Trailing slash — Some tools are sensitive to a trailing slash. Try both with and without.
4. Wrong config file — If using Claude Desktop, make sure you are editing the correct config file.

Getting Help

If you have verified everything and the MCP server still is not responding, reach out to our support team. Please include the tool you are using, the error message, and your MCP endpoint URL (without the API key).