Crayon · OAuth Scopes

Crayon OAuth Scopes

OAuth 2.0 probed

Crayon publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Crayon API on a user’s behalf.

Tokens are issued from https://app.crayon.co/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.

Competitive IntelligenceMarket IntelligenceSales EnablementBattlecardsWin-Loss AnalysisProduct MarketingArtificial IntelligenceMCP

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://app.crayon.co/oauth/authorize/

Token URL
https://app.crayon.co/oauth/token/

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp:read	Read access to the Crayon competitive-intelligence MCP server at https://mcp.crayon.co/mcp/. The only scope Crayon's authorization server advertises; no write or admin scope is published.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-14'
method: probed
source: https://mcp.crayon.co/.well-known/oauth-authorization-server
docs: null
note: >-
  Read from Crayon's RFC 8414 authorization-server metadata, which is served anonymously. Crayon
  publishes no scopes/permissions reference page, so the metadata is the only scope surface. Note
  that the RFC 9728 protected-resource document for the MCP endpoint declares an EMPTY
  scopes_supported array while the authorization server declares mcp:read — the two disagree, and
  that disagreement is recorded rather than reconciled. The earlier version of this file described
  the "CustomerApi" scope of Crayon Group ASA's Cloud-iQ platform (crayon.com), a different
  company; it is quarantined in _wrong-company/.

schemes:
- name: CrayonOAuth2
  source: well-known/crayon-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app.crayon.co/oauth/authorize/
    tokenUrl: https://app.crayon.co/oauth/token/

scopes:
- scope: mcp:read
  description: >-
    Read access to the Crayon competitive-intelligence MCP server at
    https://mcp.crayon.co/mcp/. The only scope Crayon's authorization server advertises; no
    write or admin scope is published.
  flows:
  - authorizationCode
  sources:
  - https://mcp.crayon.co/.well-known/oauth-authorization-server
  - https://app.crayon.co/.well-known/oauth-authorization-server

discrepancies:
- resource: https://mcp.crayon.co/mcp/
  document: https://mcp.crayon.co/.well-known/oauth-protected-resource/mcp/
  issue: scopes_supported is [] on the protected resource but ["mcp:read"] on the authorization server
  observed: '2026-08-14'

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