Auth Proxy MCP Server
OAuth 2.1 authorization for private MCP servers using OIDC providers.
Data last scanned today · Reviewed today
Overview
Auth Proxy MCP Server functions as an authorization layer that sits in front of existing MCP servers. By acting as an OAuth 2.1 server that integrates with any OIDC-compliant identity provider, it allows you to secure private MCP backends without modifying the internal authentication logic of those services. Deployment is handled via a containerized service that requires a Redis instance for managing authorization codes and refresh-rotation tokens. It supports major OIDC providers such as Microsoft Entra, Keycloak, Auth0, and Okta, enabling standard-compliant authentication flows for AI-driven development tools.
Our verdict
This server carries a high risk level with a security score of 45/100. Because this project is community-maintained rather than vendor-official and includes no read-only mode, users should exercise caution before deploying it in sensitive environments. It is recommended for developers who need to bridge authentication gaps in custom MCP setups, provided they are prepared to manage the security configurations manually.
- Supports OIDC-compliant authentication providers
- Zero direct dependencies reduce supply-chain surface
- Licensed under the permissive Apache-2.0 license
- High security risk level score
- Lacks a read-only execution mode
- Maintained by community contributors rather than an official vendor
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the core infrastructure requirements for running the proxy?
You need an OIDC-compliant Identity Provider (IdP) with discovery enabled, Redis version 7 or higher for production state management, and a publicly accessible HTTPS endpoint.
›Do I need to modify my existing MCP server to work with this proxy?
No, the proxy is designed to sit in front of an unmodified upstream MCP server, handling all OAuth 2.1 authentication requirements.
›Is Redis mandatory for all deployments?
Yes, Redis is required by default to ensure security features like single-use authorization codes and refresh token rotation detection work consistently across container replicas.
›Which OIDC identity providers are supported?
The proxy supports any OIDC-compliant IdP, including Keycloak, Microsoft Entra ID, Auth0, Okta, and Google, as it relies on standard OIDC auto-discovery.
›How is the proxy configured?
All configuration is managed via environment variables. The required settings include your OIDC issuer details, client credentials, the proxy base URL, the upstream MCP server URL, a token signing secret, and a connection string for Redis.
›Does the server require specific networking or TLS setups?
The server expects public HTTPS termination at your ingress, which should point to the proxy's listen address. The proxy, your IdP, and your MCP clients must all be able to reach the configured PROXY_BASE_URL over the network.
Badge
Maintain this server? Add the live badge to your README.