MCP_SERVER_INVALID_ENDPOINT

Issue

The URL responded, but not as an MCP server. The server returned HTTP 404 or 405, or sent a web page instead of an MCP response. The URL usually points to the wrong path, or the Transport type doesn't match the server.

Resolution

1. Check that the URL is the server's MCP endpoint, not the app's website. If the URL opens a web page or a sign-in page in your browser, it's the website. The server's documentation lists the full MCP endpoint URL. Many servers serve MCP at a path such as /mcp or /sse, not at the site root.
2. Set Transport type to match the endpoint. Use Streaming HTTP for a streamable HTTP server, or SSE for a server that uses Server-Sent Events (SSE).
3. Save, then click Initiate connection again.

If you see this while setting up a connector in Admin console → Platform → Connectors, check the MCP server URL and Transport type on the setup page, then click Connect again. If the setup page doesn't ask for a server URL, contact Glean Support.

For additional assistance, contact Glean Support.