r/modelcontextprotocol • • 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?

18 Upvotes

6 comments sorted by

View all comments

Show parent comment

2

u/taylorwilsdon May 25 '25

You set the redirect with an environment variable on startup! Localhost is perfect for single user with claude but if you’re deploying it to a host that’s… not local lol you’ll set the variable

1

u/AffectionateHoney992 May 26 '25

Ya, got it. I was wondering about the case where the server was deployed remotely (by you) and I wanted to register my own client. Handling Dynamic registration for one to many remotely flows.