SUPER STUDIO · OAuth Scopes

SUPER STUDIO OAuth Scopes

OAuth 2.0 probed

SUPER STUDIO 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.

CompanyE-CommerceCommerceSubscription CommerceOrder ManagementMarketing AutomationBusiness IntelligenceSoftware-as-a-ServiceArtificial IntelligenceAgentsMCPJapan

Scopes: 0 Flows: Method: probed

Scopes (0)

SUPER STUDIO 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.

Read directly from the ecforce AI MCP authorization server's RFC 8414 metadata, which is served anonymously. The server advertises exactly one scope. No scopes/permissions reference page is published — the ecforce v2 REST API uses a member-permission model configured per API connection user in the admin screens rather than OAuth scopes, and that configuration is behind the tenant login. derive-oauth-scopes.py was not applicable: there is no OpenAPI in this repo to derive from.

📄 Provider scope reference: https://ec-force.com/information/20260804

Source

OAuth Scopes

generated: '2026-08-29'
method: probed
source: https://agent.ec-force.com/.well-known/oauth-authorization-server
docs: https://ec-force.com/information/20260804
note: >-
  Read directly from the ecforce AI MCP authorization server's RFC 8414 metadata, which is served
  anonymously. The server advertises exactly one scope. No scopes/permissions reference page is
  published — the ecforce v2 REST API uses a member-permission model configured per API connection
  user in the admin screens rather than OAuth scopes, and that configuration is behind the tenant
  login. derive-oauth-scopes.py was not applicable: there is no OpenAPI in this repo to derive from.
authorization_server: https://agent.ec-force.com
flows:
- type: authorization_code
  authorization_url: https://agent.ec-force.com/mcp/oauth/authorize
  token_url: https://agent.ec-force.com/mcp/oauth/token
  refresh_supported: true
  pkce: S256
  dynamic_client_registration: https://agent.ec-force.com/mcp/oauth/register
scopes:
- name: mcp
  description: >-
    The single scope advertised by the ecforce AI MCP authorization server. Effective authority is
    not carried in the scope string: the provider states access is bounded by the ecforce services
    the tenant has contracted and by the signed-in ecforce account's own permission scope, so two
    tokens carrying "mcp" can reach different data.
  source: oauth-authorization-server metadata
scope_count: 1

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/super-studio-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.