Sitefire · OAuth Scopes

Sitefire OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/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.

CompanyGenerative Engine OptimizationAI VisibilityMarketingSEOAnalyticsArtificial IntelligenceContent GenerationMCPAgent

Scopes: 5 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/oauth/authorize

Token URL
https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/oauth/token

Flows
authorizationCode

Scopes (5)

Scope	Description	Flows
openid	OpenID Connect sign-in; issues an ID token identifying the Sitefire user.	authorizationCode
profile	Basic profile claims (name, picture, preferred_username, updated_at).	authorizationCode
email	Email address and email_verified claim.	authorizationCode
phone	Phone number and phone_number_verified claim.	authorizationCode
offline_access	Issues a refresh token so an agent can keep a long-lived MCP session.	authorizationCode

📄 Provider scope reference: https://sitefire.ai/docs/mcp.md

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/.well-known/oauth-authorization-server
docs: https://sitefire.ai/docs/mcp.md
notes: >-
  Sitefire publishes no scope or permission reference page. The scopes below were
  read from the RFC 8414 authorization-server metadata that Sitefire's own MCP
  protected-resource document points at. They are the identity scopes of the
  Supabase authorization server Sitefire delegates sign-in to - openid/profile/
  email/phone/offline_access - not Sitefire-defined resource scopes. In other
  words the MCP server authenticates the user but does not appear to publish a
  granular authorization surface: there is no read-vs-write split between the
  seven read tools and the three write tools (create_action, write_article) in
  mcp/sitefire-mcp.yml. Recorded as an honest measurement of what is published,
  not as a claim that Sitefire ships scoped authorization.
  derive-oauth-scopes.py returned zero, because the only OpenAPI in the repo
  declares no oauth2 securityScheme.
resource: https://app.sitefire.ai/api/mcp
schemes:
- name: mcp-oauth
  source: https://app.sitefire.ai/api/mcp/oauth-metadata
  flows:
  - flow: authorizationCode
    authorizationUrl: https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/oauth/authorize
    tokenUrl: https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/oauth/token
scopes:
- scope: openid
  description: OpenID Connect sign-in; issues an ID token identifying the Sitefire user.
  flows: [authorizationCode]
  sources: [authorization-server-metadata]
  provider_defined: false
- scope: profile
  description: Basic profile claims (name, picture, preferred_username, updated_at).
  flows: [authorizationCode]
  sources: [authorization-server-metadata]
  provider_defined: false
- scope: email
  description: Email address and email_verified claim.
  flows: [authorizationCode]
  sources: [authorization-server-metadata]
  provider_defined: false
- scope: phone
  description: Phone number and phone_number_verified claim.
  flows: [authorizationCode]
  sources: [authorization-server-metadata]
  provider_defined: false
- scope: offline_access
  description: Issues a refresh token so an agent can keep a long-lived MCP session.
  flows: [authorizationCode]
  sources: [authorization-server-metadata]
  provider_defined: false
resource_scopes: []
resource_scopes_note: >-
  No Sitefire-defined resource scopes were found. The protected-resource
  metadata at /api/mcp/oauth-metadata carries no scopes_supported member, and no
  scope reference page exists in the docs or in the sitefire-ai/skills repo.
x-evidence:
- url: https://qhfesxmsojjleewjufcn.supabase.co/auth/v1/.well-known/oauth-authorization-server
  http_status: 200
  checked: '2026-08-13'
- url: https://app.sitefire.ai/api/mcp/oauth-metadata
  http_status: 200
  checked: '2026-08-13'