# Open MCP Auth Proxy The Open MCP Auth Proxy is a lightweight proxy designed to sit in front of MCP servers and enforce authorization in compliance with the [Model Context Protocol authorization](https://spec.modelcontextprotocol.io/specification/2025-03-26/basic/authorization/) requirements. It intercepts incoming requests, validates tokens, and offloads authentication and authorization to an OAuth-compliant Identity Provider. ![image](https://github.com/user-attachments/assets/fc728670-2fdb-4a63-bcc4-b9b6a6c8b4ba) ## **Setup and Installation** ### **Prerequisites** * Go 1.20 or higher * A running MCP server (SSE transport supported) * An MCP client that supports MCP authorization ### **Installation** ```bash git clone https://github.com/wso2/open-mcp-auth-proxy cd open-mcp-auth-proxy go get github.com/golang-jwt/jwt/v4 go get gopkg.in/yaml.v2 go build -o openmcpauthproxy ./cmd/proxy ``` ## Using Open MCP Auth Proxy ### Quick Start Allows you to just enable authentication and authorization for your MCP server with the preconfigured auth provider powered by Asgardeo. If you don’t have an MCP server, follow the instructions given here to start your own MCP server for testing purposes. 1. Download [sample MCP server](resources/echo_server.py) 2. Run the server with ```bash python3 echo_server.py ``` #### Configure the Auth Proxy Update the following parameters in `config.yaml`. ```yaml mcp_server_base_url: "http://localhost:8000" # URL of your MCP server listen_address: ":8080" # Address where the proxy will listen ``` #### Start the Auth Proxy ```bash ./openmcpauthproxy --demo ``` The `--demo` flag enables a demonstration mode with pre-configured authentication and authorization with a sandbox powered by [Asgardeo](https://asgardeo.io/). #### Connect Using an MCP Client You can use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) to test the connection and try out the complete authorization flow. ### Use with Asgardeo Enable authorization for the MCP server through your own Asgardeo organization 1. [Register]([url](https://asgardeo.io/signup)) and create an organization in Asgardeo 2. Now, you need to authorize the OpenMCPAuthProxy to allow dynamically registering MCP Clients as applications in your organization. To do that, 1. Create an [M2M application](https://wso2.com/asgardeo/docs/guides/applications/register-machine-to-machine-app/) 1. [Authorize this application](https://wso2.com/asgardeo/docs/guides/applications/register-machine-to-machine-app/#authorize-the-api-resources-for-the-app) to invoke “Application Management API” with the `internal_application_mgt_create` scope. ![image](https://github.com/user-attachments/assets/0bd57cac-1904-48cc-b7aa-0530224bc41a) 2. Note the **Client ID** and **Client secret** of this application. This is required by the auth proxy #### Configure the Auth Proxy Create a configuration file config.yaml with the following parameters: ```yaml mcp_server_base_url: "http://localhost:8000" # URL of your MCP server listen_address: ":8080" # Address where the proxy will listen asgardeo: org_name: "" # Your Asgardeo org name client_id: "" # Client ID of the M2M app client_secret: "" # Client secret of the M2M app ``` #### Start the Auth Proxy ```bash ./openmcpauthproxy --asgardeo ``` ### Use with any standard OAuth Server Enable authorization for the MCP server with a compliant OAuth server #### Configuration Create a configuration file config.yaml with the following parameters: ```yaml mcp_server_base_url: "http://localhost:8000" # URL of your MCP server listen_address: ":8080" # Address where the proxy will listen ``` **TODO**: Update the configs for a standard OAuth Server. #### Start the Auth Proxy ```bash ./openmcpauthproxy ``` #### Integrating with existing OAuth Providers - [Auth0](URL) - Enable authorization for the MCP server through your Auth0 organization. **TODO**: Add instructions under docs and link