I'm building a self-hostable MCP auth proxy for silent token refresh, would you use it?
I've been experimenting with an MCP auth proxy that sits between the MCP client and server and handles the OAuth/token lifecycle on behalf of the client.
The basic idea:
MCP Client → Auth Proxy → MCP Server
The proxy would handle things like:
- OAuth authentication
- Access-token expiration
- Automatic/silent token refresh
- Refresh-token storage
- Multiple OAuth providers
- Client-specific OAuth quirks
- Self-hosting via Docker
The goal is that an MCP client shouldn't need to repeatedly deal with expired credentials or implement provider-specific refresh logic.
I'm considering making it open-source and self-hostable, rather than another hosted auth service.
I'm asking before building too much:
Is this actually a problem you're experiencing with MCP?
Particularly interested in people using Cursor, Claude, VS Code/Copilot, or custom MCP clients.
How are you currently handling token expiration and refresh? And what would make a proxy like this useful enough for you to actually deploy?
I'm more interested in hearing about existing pain/workarounds than getting "yes, I'd use it" answers.