MCP Auth Explained: Every Method, Direct and Through a Proxy
blog.dwornikowski.com
MCP Auth Explained: Every Method, Direct and Through a Proxy
1–8 of 8 posts
Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#2> The MCP authorization spec is written entirely around user-delegated flows and does not define a machine-to-machine grant at all.
is slightly wrong. There's a blessed extension: https://modelcontextprotocol.io/extensions/auth/oauth-client...
Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#3Enjoying this so far. > The MCP authorization spec is written entirely around user-delegated flows and does not define a machine-to-machine grant at all. is slightly wrong. There's a blessed extension: https://modelcontextprotocol.io/extensions/auth/oauth-client...
Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#4Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#5Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#6Enjoying this so far. > The MCP authorization spec is written entirely around user-delegated flows and does not define a machine-to-machine grant at all. is slightly wrong. There's a blessed extension: https://modelcontextprotocol.io/extensions/auth/oauth-client...
Re: MCP Auth Explained: Every Method, Direct and Through a Proxy
#7Enjoying this so far. > The MCP authorization spec is written entirely around user-delegated flows and does not define a machine-to-machine grant at all. is slightly wrong. There's a blessed extension: https://modelcontextprotocol.io/extensions/auth/oauth-client...
Yeah, other than that one thing, this was a great intro to MCP auth.