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.
CompanyMCPEnterprise AIData GovernanceAI AgentsData IntegrationSecurityAuthentication
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.
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
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.