Medusa · OAuth Scopes

Medusa OAuth Scopes

OAuth 2.0 probed

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

E-CommerceHeadless CommerceOpen-SourceCommerceStorefrontOrder ManagementNode.jsGraphQLAgentic CommerceMCP

Scopes: 0 Flows: Method: probed

Scopes (0)

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

There is no per-tool or per-resource scope. Access to the MCP server is all-or-nothing on a Medusa Cloud account, so an agent cannot be granted the documentation-search tool without also being granted the feedback-submission tool.

📄 Provider scope reference: https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: >-
  https://docs.medusajs.com/.well-known/oauth-authorization-server and
  https://docs.medusajs.com/.well-known/oauth-protected-resource, fetched anonymously
  2026-08-26 and saved verbatim to well-known/.
docs: https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server
description: >-
  Medusa's Store and Admin REST APIs declare NO oauth2 security scheme — they authenticate
  with a JWT bearer token, a session cookie or an Admin secret API key, none of which carry
  scopes. The only OAuth surface Medusa operates is the one in front of the remote MCP
  server, and it publishes RFC 8414 authorization-server metadata anonymously. The three
  scopes below are what that document advertises; they are identity scopes for a Medusa
  Cloud login, not commerce permissions.
applies_to:
  - medusa:medusa-mcp-server
does_not_apply_to:
  - medusa:medusa-store-api
  - medusa:medusa-admin-api
authorization_server:
  issuer: https://docs.medusajs.com
  authorization_endpoint: https://cloud.medusajs.com/oauth/authorize
  token_endpoint: https://api.prod.medusajs.cloud/v1/oauth/token
  registration_endpoint: https://docs.medusajs.com/oauth/register
  jwks_uri: https://api.prod.medusajs.cloud/.well-known/jwks.json
  grant_types_supported: [authorization_code, refresh_token]
  response_types_supported: [code]
  token_endpoint_auth_methods_supported: [none]
  code_challenge_methods_supported: [S256]
  dynamic_client_registration: true
protected_resource:
  resource: https://docs.medusajs.com
  authorization_servers: [https://docs.medusajs.com]
scopes:
  - name: openid
    description: OpenID Connect — issue an ID token identifying the Medusa Cloud account.
    source: oauth-authorization-server scopes_supported
  - name: email
    description: Access to the account's email address claim.
    source: oauth-authorization-server scopes_supported
  - name: profile
    description: Access to the account's basic profile claims.
    source: oauth-authorization-server scopes_supported
scope_count: 3
alternative_credential:
  type: personal access key
  usage: Bearer token in the Authorization header, in place of the OAuth flow.
  source: https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server
note: >-
  There is no per-tool or per-resource scope. Access to the MCP server is all-or-nothing on
  a Medusa Cloud account, so an agent cannot be granted the documentation-search tool
  without also being granted the feedback-submission tool.

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