Milana · OAuth Scopes

Milana OAuth Scopes

OAuth 2.0 searched

Milana publishes 7 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Milana API on a user’s behalf.

Tokens are issued from https://clerk.getmilana.ai/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyAISession ReplayProduct AnalyticsDeveloper ToolsAgentsSDK

Scopes: 7 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://clerk.getmilana.ai/oauth/authorize

Token URL
https://clerk.getmilana.ai/oauth/token

Flows
authorizationCode

Scopes (7)

Scope	Description	Flows
openid	OpenID Connect authentication (standard OIDC scope).	authorizationCode
profile	Access to the user's profile claims (standard OIDC scope).	authorizationCode
email	Access to the user's email address (standard OIDC scope).	authorizationCode
public_metadata	Read the user's public metadata (Clerk scoped-access scope).	authorizationCode
private_metadata	Read the user's private metadata (Clerk scoped-access scope).	authorizationCode
offline_access	Issue a refresh token for long-lived access (standard OAuth scope).	authorizationCode
user:org:read	Read the user's organization membership (Clerk scoped-access scope).	authorizationCode

📄 Provider scope reference: https://clerk.com/docs/oauth/scoped-access

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: https://app.getmilana.ai/.well-known/oauth-authorization-server
docs: https://clerk.com/docs/oauth/scoped-access
notes: >-
  Milana (formerly Vantara) publishes no OpenAPI, but its hosted MCP server at
  https://app.getmilana.ai/mcp authenticates via OAuth 2.0 against the Clerk-run
  authorization server at https://clerk.getmilana.ai. Scopes below are exactly
  the scopes_supported list from the RFC 8414 authorization-server metadata.
schemes:
  - name: OAuth2
    source: well-known/vantara-oauth-authorization-server.json
    issuer: https://clerk.getmilana.ai
    flows:
      - flow: authorizationCode
        authorizationUrl: https://clerk.getmilana.ai/oauth/authorize
        tokenUrl: https://clerk.getmilana.ai/oauth/token
        pkce: S256
        refresh_token: true
        dynamic_client_registration: https://clerk.getmilana.ai/oauth/register
scopes:
  - scope: openid
    description: OpenID Connect authentication (standard OIDC scope).
    flows: [authorizationCode]
  - scope: profile
    description: Access to the user's profile claims (standard OIDC scope).
    flows: [authorizationCode]
  - scope: email
    description: Access to the user's email address (standard OIDC scope).
    flows: [authorizationCode]
  - scope: public_metadata
    description: Read the user's public metadata (Clerk scoped-access scope).
    flows: [authorizationCode]
  - scope: private_metadata
    description: Read the user's private metadata (Clerk scoped-access scope).
    flows: [authorizationCode]
  - scope: offline_access
    description: Issue a refresh token for long-lived access (standard OAuth scope).
    flows: [authorizationCode]
  - scope: 'user:org:read'
    description: Read the user's organization membership (Clerk scoped-access scope).
    flows: [authorizationCode]