I Couldn't Find an OAuth 2.1 Proxy for MCP Servers, So I Built One

dev.to

When I started deploying custom MCP servers to connect to Claude.ai, I hit a wall fast. Claude.ai's custom connector flow requires your MCP server to implement OAuth 2.1 Protected Resource Metadata — specifically RFC 9728 — before it will even attempt to authenticate. No RFC 9728 /.well-known/oauth-protected-resource endpoint? Silent failure. No error. The connector just doesn't work. I went looking for an existing solution. Something that could sit in front of any MCP server, handle the spec

Read Full Article open_in_new
arrow_back Back to News