Marco Polo · OAuth Scopes

Marco Polo OAuth Scopes

OAuth 2.0 searched

Marco Polo uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyMCPModel Context ProtocolEnterprise AIData GovernanceAI AgentsData IntegrationSecurityOAuth

Scopes: 0 Flows: Method: searched

Scopes (0)

Marco Polo implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Scopes advertised by the MarcoPolo authorization server (WorkOS AuthKit) via RFC 8414 metadata. These are the standard OIDC/OAuth scopes; MarcoPolo does not publish application-specific resource scopes.

📄 Provider scope reference: https://docs.marcopolo.dev/getting-started

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://mcp.marcopolo.dev/.well-known/oauth-authorization-server
provider: marco-polo
docs: https://docs.marcopolo.dev/getting-started
note: >-
  Scopes advertised by the MarcoPolo authorization server (WorkOS AuthKit) via
  RFC 8414 metadata. These are the standard OIDC/OAuth scopes; MarcoPolo does not
  publish application-specific resource scopes.
scopes:
- name: openid
  description: OpenID Connect sign-in; issue an ID token.
- name: profile
  description: Access the user's basic profile claims.
- name: email
  description: Access the user's email address.
- name: offline_access
  description: Issue a refresh token for long-lived access.