Installer fails
Read the full installer output, confirm network access and Node.js/package manager requirements, and check permissions. Prefer downloading and reviewing the script before executing it. Do not paste secrets or tokens into support requests.
Control center does not open
Confirm the host process is running, check its startup logs, and verify the configured port. Ensure another application is not already using that port. The control center and MCP service may use different ports.
MCP setup or initialization fails
- Use the exact MCP endpoint path, not the marketing homepage.
- Check redirects, TLS certificate, HTTP status, content type, request methods, and required headers.
- Test initialization and tool discovery using an MCP-aware inspector.
- Confirm the server supports the transport and protocol version negotiated by the target client.
- Inspect server logs for JSON-RPC errors; do not return success-shaped placeholder results for unimplemented tools.
Tunnel or custom domain does not work
Confirm the tunnel process is online and targets the correct local port. Verify DNS points to the intended tunnel or reserved ngrok domain. Check that proxy/WAF rules are not blocking POST requests, request bodies, streaming, or required headers.
Client says the server is unavailable
Test from a separate network and compare the result with localhost. Verify the endpoint is publicly reachable, authentication matches the server configuration, and the account/client actually supports custom remote MCP. Some clients or plans may offer different capabilities.