Documentation
¶
Overview ¶
Command oauth-proxy is a generic, metadata-driven OAuth 2.0 credential manager for remote MCP servers. OAuth-only MCP servers (e.g. Slack's public MCP at https://mcp.slack.com/mcp) reject hand-pasted bearer tokens, so this sidecar discovers each server's OAuth config from its RFC 8414 metadata, exchanges a refresh token (or a one-time authorization code via PKCE) for an access token, and writes the access token into a Kubernetes Secret that an MCPServer's spec.auth.bearerToken already points the model-router at.
One binary serves any OAuth-only MCP — only the per-server Secret differs:
oauth-proxy login-url --server-url ... --client-id ... --redirect-uri ... oauth-proxy seed --server-url ... --oauth-secret ns/creds --code ... --code-verifier ... oauth-proxy run --server-url ... --oauth-secret ns/creds --access-token-secret ns/slack-mcp-token
Click to show internal directories.
Click to hide internal directories.