Buf · OAuth Scopes

Buf OAuth Scopes

OAuth 2.0 probed

Buf 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.

Code GenerationgRPCKafkaOpen SourceProtocol BuffersSchema RegistrySDKStreaming

Scopes: 0 Flows: Method: probed

Scopes (0)

Buf 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 provider's own RFC 8414 and RFC 9728 discovery documents, both fetched anonymously and saved verbatim under well-known/. There is no broader scope catalogue: the BSR's non-MCP surface uses unscoped user API tokens, so this file describes the whole of Buf's OAuth scope surface rather than a subset of it.

📄 Provider scope reference: https://buf.build/docs/bsr/apis/mcp/

Source

OAuth Scopes

generated: '2026-09-13'
method: probed
source: https://buf.build/.well-known/oauth-authorization-server
docs: https://buf.build/docs/bsr/apis/mcp/
authorization_server: https://buf.build
protected_resources:
  - resource: https://buf.build/mcp
    metadata: https://buf.build/.well-known/oauth-protected-resource/mcp
    scopes_supported: [mcp]
    bearer_methods_supported: [header]
flows:
  authorization_code:
    authorization_endpoint: https://buf.build/oauth2/authorize
    token_endpoint: https://buf.build/oauth2/token
    pkce: S256
    dynamic_client_registration: https://buf.build/oauth2/register
scopes:
  - name: mcp
    description: >-
      The only scope the BSR authorization server advertises. Granting it lets an MCP
      client call the BSR Registry API as the approving user. It is NOT a read-only or
      least-privilege scope: Buf's docs state the resulting token "has the same access as
      the user who approved it ... including writes."
    read_only: false
    source: https://buf.build/.well-known/oauth-authorization-server
scope_count: 1
note: >-
  Derived from the provider's own RFC 8414 and RFC 9728 discovery documents, both fetched
  anonymously and saved verbatim under well-known/. There is no broader scope catalogue:
  the BSR's non-MCP surface uses unscoped user API tokens, so this file describes the
  whole of Buf's OAuth scope surface rather than a subset of it.

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/buf-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.