Jam · OAuth Scopes

Jam OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://api.jam.dev/oauth/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.

CompanyDeveloper ToolsBug ReportingDebuggingQuality AssuranceObservabilityScreen RecordingModel Context Protocol
Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.jam.dev/oauth/authorize
Token URL
https://api.jam.dev/oauth/token
Flows
authorizationCode

Scopes (2)

ScopeDescriptionFlows
mcp:read Read access to Jam data (details, console logs, network requests, screenshots, transcripts, members, folders, recording links) via the MCP server and CLI. authorizationCode
mcp:write Write access via the MCP server and CLI — create comments, move Jams between folders, create/update/revoke recording links. authorizationCode

Source

OAuth Scopes

jam-scopes.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://mcp.jam.dev/.well-known/oauth-authorization-server
docs: https://jam.dev/docs/personal-access-tokens
schemes:
  - name: OAuth2
    source: https://mcp.jam.dev/.well-known/oauth-authorization-server
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.jam.dev/oauth/authorize
        tokenUrl: https://api.jam.dev/oauth/token
        pkce: S256
scopes:
  - scope: mcp:read
    description: Read access to Jam data (details, console logs, network requests, screenshots, transcripts, members, folders, recording links) via the MCP server and CLI.
    flows: [authorizationCode]
  - scope: mcp:write
    description: Write access via the MCP server and CLI — create comments, move Jams between folders, create/update/revoke recording links.
    flows: [authorizationCode]
notes: >-
  Scopes are also selectable when minting Personal Access Tokens
  (Settings -> MCP). Tokens carry the jam_pat_ prefix and are used as Bearer
  credentials for headless/CI MCP clients.