add support for proxy base path routing #733
Draft
+33
−6
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.
add support for proxy base path routing when using vscode-server port-forward proxy
Motivation and Context
When running mcpinspector from inside vscode-server and in a vm and not localhost route path is required for both the client UI (6274) and the mcp-proxy (6277)
For example I'm using aws cloudfront in front of ec2 running vscode-server, and when running
npx @modelcontextprotocol/inspector
the server is available in a url like thishttps://d2udq1bmhskoal.cloudfront.net/proxy/6274
How Has This Been Tested?
I tested this on aws with cloudfront/ec2, mcp server running on ec2 locahost as streameable http on port 8000

Here is a screenshot
Breaking Changes
No braking changes
Types of changes
Checklist
Additional context