Azure-Samples / Azure-Samples/remote-mcp-apim-functions-python

VS Code authentication fails but Inspector works

Open
#15 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
129
Forks
79
PR merge metrics
No merged PRs in 30d

Description

When using inspector, all works fine. With the preconfigured SSE MCP tool, and also with an MCP tool I added thats HTTP Stream.

However, when using the same configuration in VS code. There seems to be a problem with the redirect url.

Configuration
![Image](https://github.com/user-attachments/assets/ab62473b-be0e-4f41-92fb-46c01dd92fa2)

Redirect url:

![Image](https://github.com/user-attachments/assets/325cfe2b-a022-4288-92e8-2562d068d080)

Strange enough as well is the fact that the redirect url is insides, but im working from regular vs code.

Currently out of ideas on how to proceed and debug. Other oauth MCP tools work just fine. (GitHub).

Any ideas would be appreciated.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the OAuth redirect URL used by VS Code with the configuration that works in Inspector and with the other working OAuth MCP tools mentioned in the issue. Done means authentication completes successfully in regular VS Code for the configured SSE or HTTP Stream MCP tool.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.