Skip to main content
Applicable to: All users connecting to MCP servers via TrueFoundry Gateway. The transport change specifically impacts users connecting to MCP servers that use SSE transport.

​
What Is Changing

This release includes two changes:
  1. New MCP Gateway URLs with a tenant parameter, enabling MCP OAuth chaining.
  2. Transport protocol transparency — the gateway now preserves the transport protocol of the remote MCP server instead of always using streamable-http.

​
Smarter MCP Gateway URLs with OAuth Chaining

We’ve added a tenant parameter to MCP Gateway URLs, unlocking MCP OAuth chaining. Old URL format: 
https://your-company.truefoundry.cloud/api/llm/mcp/slack-mcp/server
New URL format: 
https://your-company.truefoundry.cloud/api/llm/your-company/mcp/slack-mcp/server

​
What This Means for You

  • The gateway now automatically chains TrueFoundry’s authentication with the remote MCP server’s own OAuth flow.
  • You can connect to MCPs from IDEs like Cursor/VSCode without providing a TrueFoundry token or authenticating to the MCP server manually in the TrueFoundry UI.
  • You only need to add a snippet like this to your IDE for MCP server:
{
  "mcpServers": {
    "linear": {
      "url": "https://gateway.truefoundry.ai/internal/mcp/linear/server"
    }
  }
}
Your old URLs continue to work without any changes. The updated URLs will appear in the “How to Use” section for MCP server on the platform going forward. The old URL support will be removed on 16th April, 2026. Let us know if you need it for a longer duration.

​
Breaking Change: MCP Gateway Transport Transparency

Previously, all clients connecting through the gateway used streamable-http — regardless of what the underlying MCP server used. Going forward, the gateway will preserve the transport protocol of the remote MCP server.
  • If the remote server uses SSE → your client will now connect via SSE.
  • If the remote server uses streamable-http → nothing changes for you.
This aligns with the MCP specification’s recommended client pattern: try streamable-http first, fall back to SSE if needed (reference implementation).

​
What You Need to Do

  • URL change: No immediate action required — old URLs continue to work. Plan to migrate to the new URL format before 16th April, 2026.
  • Transport change: If your MCP client already follows the streamable-http → SSE fallback pattern, no action is needed. Otherwise, update your client to handle SSE transport for servers that use it.
If you have any questions or run into anything unexpected, reach out and we’ll be happy to assist.