You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auth for MCP is still pretty new and evolving, so I don't know if this is high priority. Will authorization with callback be supported/ are there any workarounds to auth with the current mcp-adapter?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Checked
Feature request
Is there any plan to support authorization through ouath and redirect? For example, if I try to connect to https://mcp.atlassian.com/v1/sse thru @modelcontextprotocol/inspector, in response to GET /sse, I get 302 redirect to location=https://auth.atlassian.com/authorize?client_id=... which redirects back to authorization using oauth callback https://mcp.atlassian.com/.well-known/oauth-authorization-server
Motivation
Auth for MCP is still pretty new and evolving, so I don't know if this is high priority. Will authorization with callback be supported/ are there any workarounds to auth with the current mcp-adapter?
Proposal (If applicable)
No response
Beta Was this translation helpful? Give feedback.
All reactions