I'm exploring a self-hostable MCP authentication proxy that sits between an MCP client and MCP server and handles OAuth token management transparently.
The main problem I'm trying to solve is token expiry and re-authentication. For example, if an MCP client receives a short-lived access token, the proxy would securely handle refresh/re-authentication in the background so the client doesn't repeatedly require the user to authenticate.
The goal would be:
Self-hosted
Client-agnostic
OAuth/OIDC support
Automatic/silent token refresh
Secure token storage
Multiple MCP servers/providers
Minimal changes required on the MCP client side
I'm particularly interested in the Atlassian MCP use case because I've seen discussions around short-lived tokens, OAuth configuration, and clients requiring repeated authentication.
Would something like this actually solve a problem for you?
If you've built or are building a custom MCP client, I'd especially like to know how you're currently handling token expiration and refresh.
