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
https://api.jam.dev/oauth/authorize
Token URL
https://api.jam.dev/oauth/token
https://api.jam.dev/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (2)
| Scope | Description | Flows |
|---|---|---|
| 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 |
📄 Provider scope reference: https://jam.dev/docs/personal-access-tokens