Bugsnag · OAuth Scopes

Bugsnag OAuth Scopes

OAuth 2.0 probed

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

MonitoringObservabilityError MonitoringApplication Performance MonitoringDistributed TracingDeveloper ToolsSmartBear
Scopes: 0 Flows: Method: probed

Scopes (0)

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

📄 Provider scope reference: https://developer.smartbear.com/smartbear-mcp/docs/remote-mcp-servers

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-17'
method: probed
source: https://oauth.bugsnag.com/.well-known/oauth-authorization-server
docs: https://developer.smartbear.com/smartbear-mcp/docs/remote-mcp-servers
description: >-
  BugSnag's OAuth surface is the authorization server behind the remote MCP
  server (bugsnag.mcp.smartbear.com). The REST Data Access API itself does not
  use OAuth — it authenticates with a personal auth token (see
  authentication/bugsnag-authentication.yml). Scopes below are read verbatim
  from the RFC 8414 authorization-server metadata document, not inferred.
authorization_server: https://oauth.bugsnag.com
issuer: https://oauth.bugsnag.com
endpoints:
  authorization: https://oauth.bugsnag.com/authorize
  token: https://oauth.bugsnag.com/token
  registration: https://oauth.bugsnag.com/register
  jwks: https://oauth.bugsnag.com/.well-known/jwks.json
flows:
  - authorization_code
  - refresh_token
pkce:
  required_methods:
    - S256
dynamic_client_registration: true
token_endpoint_auth_methods:
  - client_secret_post
  - none
scopes:
  - name: api
    description: >-
      Access to the BugSnag API on behalf of the authenticated user. Declared in
      scopes_supported; the provider publishes no per-resource breakdown of what
      it covers, so no finer decomposition is recorded here.
  - name: openid
    description: OpenID Connect sign-in scope, requesting an ID token.
  - name: profile
    description: Standard OIDC profile claims for the authenticated user.
scope_count: 3
notes:
  - >-
    scopes_supported is coarse — one `api` scope covers the whole surface. An
    agent cannot request read-only access to BugSnag over OAuth today.
  - >-
    The authorization server advertises no /.well-known/openid-configuration
    (404) despite supporting the openid scope.

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