cloro · OAuth Scopes

cloro OAuth Scopes

OAuth 2.0 probed

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

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.

CompanySearchAIWeb ScrapingSERPGenerative Engine OptimizationSEOBrand MonitoringMarket ResearchData ExtractionMCP

Scopes: 3 Flows: Method: probed

Scopes (3)

Scope	Description	Flows
profile	OpenID Connect profile claims (name, given_name, family_name, picture, preferred_username) for the signed-in cloro user. Listed in scopes_supported of the protected-resource document.
email	The signed-in user's email and email_verified claims. Listed in scopes_supported of the protected-resource document.
user:org:read	Read the user's organization membership (org_id claim) so the MCP server can bill tool calls to the organization selected at sign-in ("select the organization whose credits pay for the calls"). Listed in scopes_supported of both the protected-resource and the authorization-server documents.

📄 Provider scope reference: https://cloro.dev/docs/integrations/mcp

Source

OAuth Scopes

generated: '2026-10-07'
method: probed
source: https://mcp.cloro.dev/.well-known/oauth-protected-resource (HTTP 200, 2026-10-07); https://clerk.cloro.dev/.well-known/oauth-authorization-server (HTTP 200, 2026-10-07); https://cloro.dev/docs/integrations/mcp
docs: https://cloro.dev/docs/integrations/mcp
applies_to: cloro MCP server (https://mcp.cloro.dev/mcp) only. The REST API at api.cloro.dev uses a bearer API key with no OAuth and no per-key scopes ("per-key scopes are not available, so a client cannot request a narrower permission" - openapi/cloro-dev-openapi.yml bearerAuth description).
resource: https://mcp.cloro.dev/mcp
authorization_servers:
- https://clerk.cloro.dev
authorization_server_metadata:
  issuer: https://clerk.cloro.dev
  authorization_endpoint: https://clerk.cloro.dev/oauth/authorize
  token_endpoint: https://clerk.cloro.dev/oauth/token
  revocation_endpoint: https://clerk.cloro.dev/oauth/token/revoke
  device_authorization_endpoint: https://clerk.cloro.dev/oauth/device_authorization
  jwks_uri: https://clerk.cloro.dev/.well-known/jwks.json
  grant_types_supported: [authorization_code, refresh_token, 'urn:ietf:params:oauth:grant-type:device_code']
  code_challenge_methods_supported: [S256]
  token_endpoint_auth_methods_supported: [client_secret_basic, none, client_secret_post]
  client_id_metadata_document_supported: true
scopes:
- name: profile
  description: OpenID Connect profile claims (name, given_name, family_name, picture, preferred_username) for the signed-in cloro user. Listed in scopes_supported of the protected-resource document.
- name: email
  description: The signed-in user's email and email_verified claims. Listed in scopes_supported of the protected-resource document.
- name: user:org:read
  description: Read the user's organization membership (org_id claim) so the MCP server can bill tool calls to the organization selected at sign-in ("select the organization whose credits pay for the calls"). Listed in scopes_supported of both the protected-resource and the authorization-server documents.
authorization_server_only_scopes:
- openid
- public_metadata
- private_metadata
- offline_access
note: Scope descriptions are derived from the Clerk authorization-server metadata (claims_supported) and the provider's MCP page; cloro publishes no separate scopes reference. Tokens are verified by the MCP server against the issuer's JWKS; the API key path (Authorization Bearer or key-in-URL) needs no scopes.

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/cloro-dev-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.