I’m building a self-hostable MCP authentication proxy designed to handle OAuth authentication and silent token refresh transparently for MCP clients.
The idea is simple: instead of implementing authentication, token storage, refresh logic, and provider-specific OAuth flows separately in every MCP client, the proxy sits between the client and MCP server and handles that complexity automatically.
I’m particularly interested in whether this solves a real pain point for developers building MCP-based applications.
Would you use something like this?
What authentication problems are you currently running into with MCP, especially around OAuth, token expiration, refresh, and multi-provider support?
Looking for honest feedback before I take it further.