Browser Use · OAuth Scopes

Browser Use OAuth Scopes

OAuth 2.0 probed

Browser Use 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.

AI AutomationBrowser AutomationWeb AgentsWeb ScrapingHeadless BrowsersAgent InfrastructureMCPCloud Browsers
Scopes: 0 Flows: Method: probed

Scopes (0)

Browser Use 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.

Derived from the live OAuth 2.0 authorization-server metadata, not from an OpenAPI oauth2 securityScheme — none of the three published OpenAPI documents declares an oauth2 flow. The authorization server exists to protect the hosted MCP resource, and it advertises exactly one scope.

📄 Provider scope reference: https://browser-use.com/auth.md

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-29'
method: probed
source: https://browser-use.com/.well-known/oauth-authorization-server
docs: https://browser-use.com/auth.md
note: >-
  Derived from the live OAuth 2.0 authorization-server metadata, not from an OpenAPI oauth2
  securityScheme — none of the three published OpenAPI documents declares an oauth2 flow. The
  authorization server exists to protect the hosted MCP resource, and it advertises exactly one scope.
authorization_server:
  issuer: https://api.browser-use.com
  metadata_url: https://browser-use.com/.well-known/oauth-authorization-server
  http_status: 200
  protected_resource: https://api.browser-use.com/mcp
  protected_resource_metadata_url: https://api.browser-use.com/.well-known/oauth-protected-resource
  http_status_protected_resource: 200
  dynamic_client_registration: true
  grant_types:
  - authorization_code
  - urn:ietf:params:oauth:grant-type:device_code
  code_challenge_methods:
  - S256
scope_count: 1
scopes:
- name: mcp
  description: >-
    Access the Browser Use hosted MCP resource at https://api.browser-use.com/mcp. This is the only
    permission published in the authorization-server metadata.
  resource: https://api.browser-use.com/mcp
  source: https://browser-use.com/.well-known/oauth-authorization-server
gaps:
- >-
  No per-operation or per-resource scopes are published for the v2/v3/v4 REST APIs. An API key is
  all-or-nothing against a project, which is a real constraint for agent delegation.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/browser-use-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.