Claude managed MCP connector redirect error: Sume final URL

Use the final address, https://mcp.sume.com/mcp, with no shortener, proxy or alias in front of it. Claude Desktop builds v1.46388.0 (2026-09-04) and v2.2553.0 (2026-09-17) stopped following HTTP redirects for managed MCP connections, and a URL that redirects now reports a configuration error.

If an admin pushed a managed connector for Sume and users now see that error, the first thing to check is whether the pushed URL is the documented endpoint or an older link that forwards somewhere.

What changed

Per the changelog, managed MCP connections no longer follow redirects. The error message points at configuration rather than at the server, so it can be mistaken for an authentication problem.

At a glance

What to put in the managed list

Sume documents one hosted endpoint for MCP, https://mcp.sume.com/mcp. Put that string in the managed server entry and nothing else. Authentication is separate: OAuth with the mcp:read scope required and mcp:write opt-in, or an API key sent as a Bearer token or x-api-key header.

After changing the entry, restart the connector and run tools_list or mcp_health from a conversation to confirm the connection.

• Do not use a link-tracking or vanity URL for the endpoint.
• Do not add a trailing path other than /mcp.
• Test with mcp_health before rolling out to a team.

Limits and what is not verified

The changelog does not list which redirect status codes are affected, and I did not verify whether Sume's endpoint ever redirects. The advice is to use the documented address so the question never arises.