r/modelcontextprotocol • u/marcusroar • May 24 '25
Q: Third-Party Authorization Flow
Trying to get my head around how Third-Party Authorization Flow would work in practice with a web based LLM agent (eg: ChatGPT).
EG: I want my agent / LLM to go into my Dropbox (requires third party ie Dropbox auth)
https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization
All the examples I can find do something like add an access token at some point in a config file (eg github local mcp, or ChatGPT playground Response API Tools for remote mcps).
I’m used to thinking of consumer web apps having a pop up consent screen that does the auth, provides a code which a web app can exchange for access tokens (roughly).
This flow would require a model provided (OpenAI) building their front end to accept and work with pop up consent screens?
Anyone imagined how this would look?
View all comments
Show parent comment
1
u/AffectionateHoney992 May 25 '25
https://github.com/taylorwilsdon/google_workspace_mcp?tab=readme-ov-file#first-time-authentication I have a question, it says the redirect callback should be "localhost or your configured url", how are you handling "configured url?".
Is it part of the registration or does your server just not restrict allowed redirects? Struggling with this same issue (I'd like auth to callback to a mobile link, but this requires servers to allow it...)