Driver · OAuth Scopes

Driver OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://api.us1.driverai.com/mcp/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.

CompanyAIDeveloper ToolsCode DocumentationMCPCodebase IntelligenceAgentsDeveloper Experience

Scopes: 3 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.us1.driverai.com/mcp/authorize

Token URL
https://api.us1.driverai.com/mcp/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
openid	OpenID Connect authentication of the acting user.	authorizationCode
profile	Access to the user's basic profile.	authorizationCode
email	Access to the user's email address.	authorizationCode

📄 Provider scope reference: https://www.driver.ai/docs/mcp-setup

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://api.us1.driverai.com/.well-known/oauth-authorization-server
docs: https://www.driver.ai/docs/mcp-setup
schemes:
- name: oauth2
  source: https://api.us1.driverai.com/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.us1.driverai.com/mcp/authorize
    tokenUrl: https://api.us1.driverai.com/mcp/token
    pkce: S256
scopes:
- scope: openid
  description: OpenID Connect authentication of the acting user.
  flows: [authorizationCode]
- scope: profile
  description: Access to the user's basic profile.
  flows: [authorizationCode]
- scope: email
  description: Access to the user's email address.
  flows: [authorizationCode]
notes: >-
  The MCP OAuth 2.1 authorization server advertises only identity scopes
  (openid/profile/email). Resource authorization is enforced by Driver's
  role-based access model (Source Admin / Source Member, direct or team-
  inherited), not by OAuth scopes. Personal access tokens inherit the user's
  role; machine keys are granted per source.