-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Description
Inspector Version
- 2.21.1
Describe the bug
When doing the OAuth DCR request, it doesn't go to a proxy, which can cause a CORS errors on OAuth providers that do not allows CORS for DCR.
To Reproduce
Steps to reproduce the behavior:
- Use an MCP server that supports DCR
- Check where the DCR request is sent, it is sent directly from the browser instead of going via the proxy even when the proxy connection is enabled.
Expected behavior
I expect all such requests to go via the proxy.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- OS: macOS
- Browser: Google Chrome
Additional context
Add any other context about the problem here.
Version Consideration
Inspector V2 is under development to address architectural and UX improvements. During this time, V1 contributions should focus on bug fixes and MCP spec compliance. See CONTRIBUTING.md for more details.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels