Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| MCP-compatible server | ✅ | Server must support OAuth 2.0 with dynamic discovery (RFC 8414, RFC 9728). |
| OAuth endpoints | ✅ | Server must expose /.well-known/oauth-authorization-server endpoint. |
| PKCE support | ✅ | Required for secure public client authentication. |
Setup guide
No setup guide yet.Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Github’s remote MCP doesn’t follow the specification exactly so won’t work using those provider
Useful links
- Model Context Protocol Specification
- MCP GitHub Repository
- RFC 8414: OAuth 2.0 Authorization Server Metadata
- RFC 9728: OAuth 2.0 Protected Resource Metadata Discovery
- MCP Server Examples
Contribute useful links by editing this page
API gotchas
- Dynamic Discovery: MCP Generic automatically discovers OAuth endpoints from the MCP server’s
/.well-known/oauth-authorization-serverendpoint. - No Pre-configuration: No need to pre-configure OAuth client credentials. Clients are registered dynamically during the authorization flow.
- PKCE Required: All MCP Generic flows use PKCE for security. Client secrets are not used.
- Server URL Format: Always provide the full MCP server URL (e.g.,
https://api.example.com/mcp, notapi.example.com). - Automatic Scopes: OAuth scopes are automatically discovered from MCP server metadata.
Contribute API gotchas by editing this page