Sigma Computing · OAuth Scopes

Sigma Computing OAuth Scopes

OAuth 2.0 searched

Sigma Computing 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.

Business IntelligenceAnalyticsEmbedded AnalyticsData ModelingData WarehouseReportingSpreadsheetsMCPAI AgentsSnowflakeDatabricksData Governance
Scopes: 0 Flows: Method: searched

Scopes (0)

Sigma Computing 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://help.sigmacomputing.com/docs/use-sigma-mcp-server

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-27'
method: searched
source: https://api.sigmacomputing.com/.well-known/oauth-authorization-server + https://help.sigmacomputing.com/reference/get-started-sigma-api
docs: https://help.sigmacomputing.com/docs/use-sigma-mcp-server
summary: 'Sigma runs two distinct OAuth surfaces and only one of them uses scopes. The REST API clientCredentials flow declares
  an EMPTY scopes object in the OpenAPI: authorization is carried entirely by the Sigma account type and object-level grants
  attached to the member the credentials belong to. The MCP server, by contrast, advertises real scopes in RFC 8414 metadata.'
surfaces:
- surface: REST API (clientCredentials)
  scope_model: none
  scopes: []
  note: components.securitySchemes.oauth2.flows.clientCredentials.scopes == {} in both published specs. Not an omission
    we can fill — Sigma genuinely does not scope REST tokens.
- surface: MCP server (authorization_code + PKCE)
  scope_model: declared
  metadata_url: https://api.sigmacomputing.com/.well-known/oauth-authorization-server
  scopes:
  - name: mcp:access
    description: Access the Sigma MCP server. Named as the required scope in the RFC 9728 WWW-Authenticate challenge returned
      by POST https://api.sigmacomputing.com/mcp.
  - name: api:access
    description: Access the Sigma REST API through the same authorization server. Advertised in scopes_supported; not required
      by the MCP protected-resource metadata.
authorization_model:
  primary: Sigma account types (Admin, Creator, Explorer, Viewer and custom types) gate which API operations a member may
    call at all.
  object_level: Folder and document permissions (Can view / Can explore / Can edit / Owner) and connection permissions (Can
    use / Can annotate / Can write) gate which objects those operations may touch.
  row_and_column: User attributes drive row-level security; column-level security rules are set per data model element.
  docs:
  - https://help.sigmacomputing.com/docs/account-type-and-license-overview
  - https://help.sigmacomputing.com/docs/folder-and-document-permissions
  - https://help.sigmacomputing.com/docs/user-attributes
  - https://help.sigmacomputing.com/docs/column-level-security

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/sigma-computing-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 email required.

GitHub Google LinkedIn

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