fix: normalize MCP server URLs by removing trailing slashes #9123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR attempts to address Issue #9120. Feedback and guidance are welcome.
Problem
MCP servers fail to connect when the URL includes a trailing slash (e.g.,
https://api.githubcopilot.com/mcp/), returning a 405 non-200 response error. This creates friction for developers migrating from Cursor, which automatically normalizes URLs by removing trailing slashes.Solution
Implemented URL normalization for both streamable-http and SSE type MCP servers by removing trailing slashes before creating the transport connections.
Changes
Testing
All tests pass successfully:
Fixes
Fixes #9120
Important
Normalize MCP server URLs by removing trailing slashes to prevent connection errors, with comprehensive tests added.
McpHub.tsforstreamable-httpandsseconnections.McpHub.spec.tsfor URL normalization.streamable-httpandsseserver types are tested.This description was created by
for f1990ff. You can customize this summary. It will automatically update as commits are pushed.