Status: [LIVE] Endpoints found: https://claude.ai/api/mcp/auth_callback Source: https://github.com/stephaneberle9/authsome-mcp-proxy # Authsome MCP Proxy A [Model Context Protocol](https://modelcontextprotocol.io) (MCP) proxy that bridges *upstream MCP servers protected by token validation or static credentials* to MCP clients such as Claude Desktop, Claude Code, Cursor, Codex, MCP Inspector, and Claude.ai. ("Authsome" as in *awesome*, but with auth.) The proxy can run as: - **Web mode** (`--transport http`, **recommended for end users**) — a persistent HTTP server that any MCP client reaches by URL. Downstream clients sign in through the standard MCP OAuth flow; the proxy bridges it to your IdP and forwards traffic upstream. A single instance can serve many users simultaneously and lives behind a normal URL (`https://mcp.example.com/mcp`) — no per-user config files, subprocess launchers, or local Python toolchains. This is the default for non-developer rollouts and the only mode that works with web-only clients like Claude.ai. - **Desktop mode** (`--transport stdio`, the default for backwards compatibility, **developer use**) — launched as a subprocess by the MCP client (Claude Desktop, Cursor, Codex, Claude Code via `claude mcp add --transport stdio`). Each user runs their own instance and the proxy performs the OAuth flow against an external OIDC IdP on their behalf. Useful when you don't have a server to host the proxy on or when the upstream MCP only validates tokens and you want each developer to authenticate locally. - [What Is This For?](#what-is-this-for) - [Prerequisites](#prerequisites) - [Web Mode (Recommended)](#web-mode-recommended) - [How it works](#how-it-works) - [Proxy as authorization server](#proxy-as-authorization-server) - [Generic OIDC](#generic-oidc) - [AWS Cognito](#aws-cognito) - [Google](#google) - [Azure (Entra ID)](#azure-entra-id) - [ZITADEL](#zitadel) - [IdP as authorization server](#idp-as-authorization-server) - [Keycloak](#keycloak) - [Connecting downstream MCP clients