Scratchpad · OAuth Scopes

Scratchpad OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://mcp.clearskies.cc/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.

CompanyProductivitySalesCRMSalesforceRevenue OperationsArtificial IntelligenceSaaSMCPModel Context ProtocolAgentsSales Intelligence

Scopes: 3 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://mcp.clearskies.cc/oauth/authorize

Token URL
https://mcp.clearskies.cc/oauth/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
openid	OpenID Connect - issue an ID token identifying the subject.	authorizationCode
profile	Basic profile claims for the authenticated user.	authorizationCode
email	Email address claim for the authenticated user; the Clearskies connect flow authenticates a team member by their email domain.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://mcp.clearskies.cc/.well-known/oauth-authorization-server
note: >-
  Scopes are read from the live RFC 8414 authorization-server metadata and the RFC 9728
  protected-resource metadata on the Clearskies MCP host; both advertise the same three. Clearskies
  publishes no scopes or permissions reference page, so there is nothing to enrich these with. The
  authorization surface is identity-only: the three OIDC scopes establish who the caller is, and the
  data a token can reach is then governed inside the workspace by the per-source connections and the
  permissions of the underlying system (Salesforce, HubSpot, Gong, Slack and the rest), not by an
  OAuth scope string. There is no read/write or per-object scope vocabulary to record.

schemes:
- name: ClearskiesMCPOAuth
  source: well-known/scratchpad-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.clearskies.cc/oauth/authorize
    tokenUrl: https://mcp.clearskies.cc/oauth/token

scopes:
- scope: openid
  description: OpenID Connect - issue an ID token identifying the subject.
  flows: [authorizationCode]
  sources: [well-known/scratchpad-oauth-authorization-server.json, well-known/scratchpad-oauth-protected-resource.json]
- scope: profile
  description: Basic profile claims for the authenticated user.
  flows: [authorizationCode]
  sources: [well-known/scratchpad-oauth-authorization-server.json, well-known/scratchpad-oauth-protected-resource.json]
- scope: email
  description: Email address claim for the authenticated user; the Clearskies connect flow
    authenticates a team member by their email domain.
  flows: [authorizationCode]
  sources: [well-known/scratchpad-oauth-authorization-server.json, well-known/scratchpad-oauth-protected-resource.json]

scope_count: 3

x-evidence:
- fetched: '2026-08-13'
  url: https://mcp.clearskies.cc/.well-known/oauth-authorization-server
  http_status: 200
- fetched: '2026-08-13'
  url: https://mcp.clearskies.cc/.well-known/oauth-protected-resource
  http_status: 200