generated: '2026-09-20'
method: searched
source: >-
  https://api.maxvideoai.com/.well-known/oauth-authorization-server,
  https://api.maxvideoai.com/.well-known/oauth-protected-resource/mcp,
  https://maxvideoai.com/docs/mcp
summary:
  types: [oauth2]
  oauth2_version: '2.1'
  oauth2_flows: [authorizationCode]
  api_key_in: []
  notes: >-
    Access to the MCP server is exclusively via OAuth 2.1 (authorization code +
    PKCE). No API keys, bearer tokens, query params or passwords are appended to
    the endpoint URL. There is no REST API and no customer API-key surface.
schemes:
- name: OAuth2
  type: oauth2
  flow: authorizationCode
  authorization_endpoint: https://vujvontfztdzszylnsyc.supabase.co/auth/v1/oauth/authorize
  token_endpoint: https://vujvontfztdzszylnsyc.supabase.co/auth/v1/oauth/token
  registration_endpoint: https://vujvontfztdzszylnsyc.supabase.co/auth/v1/oauth/clients/register
  issuer: https://api.maxvideoai.com
  pkce: S256
  dynamic_client_registration: true
  grant_types: [authorization_code, refresh_token]
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post, none]
  bearer_methods: [header]
  scopes: [openid, email, profile, offline_access]
  sources:
  - well-known/maxvideoai-oauth-authorization-server.json
  - well-known/maxvideoai-oauth-protected-resource-mcp.json
docs: https://maxvideoai.com/docs/mcp