Evermuse · OAuth Scopes

Evermuse OAuth Scopes

OAuth 2.0 searched

Evermuse 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 Evermuse API on a user’s behalf.

Tokens are issued from https://api.evermuse.com/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.

CompanyProduct ManagementCustomer FeedbackVoice of CustomerArtificial IntelligenceData IngestionProduct AnalyticsMCPDeveloper Tools

Scopes: 3 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.evermuse.com/oauth/authorize

Token URL
https://api.evermuse.com/oauth/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
mcp:read	Read access via the Evermuse MCP server (query customer evidence, roadmap, insights).	authorizationCode
mcp:write	Write access via the Evermuse MCP server.	authorizationCode
mcp:thirdparty	Third-party / delegated access via the Evermuse MCP server.	authorizationCode

📄 Provider scope reference: https://docs.evermuse.com/authentication

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: well-known/evermuse-oauth-authorization-server.json
docs: https://docs.evermuse.com/authentication
note: |-
  OAuth 2.1 scopes gate the hosted Evermuse MCP server (https://api.evermuse.com/api/mcp),
  not the REST Ingestion API (which uses `x-api-key` keys carrying `api:read`/`api:write`
  permissions). Scopes are advertised in the RFC 8414 authorization-server metadata and
  the RFC 9728 protected-resource metadata.
schemes:
- name: EvermuseOAuth
  source: well-known/evermuse-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.evermuse.com/oauth/authorize
    tokenUrl: https://api.evermuse.com/oauth/token
    pkce: S256
scopes:
- scope: mcp:read
  description: Read access via the Evermuse MCP server (query customer evidence, roadmap, insights).
  flows: [authorizationCode]
  sources: [well-known/evermuse-oauth-authorization-server.json]
- scope: mcp:write
  description: Write access via the Evermuse MCP server.
  flows: [authorizationCode]
  sources: [well-known/evermuse-oauth-authorization-server.json]
- scope: mcp:thirdparty
  description: Third-party / delegated access via the Evermuse MCP server.
  flows: [authorizationCode]
  sources: [well-known/evermuse-oauth-authorization-server.json]