Raindrop · OAuth Scopes

Raindrop OAuth Scopes

OAuth 2.0 searched

Raindrop uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyAIAgentsObservabilityMonitoringLLMOpsDeveloper ToolsTracing
Scopes: 0 Flows: Method: searched

Scopes (0)

Raindrop implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

OAuth/OIDC scopes advertised by Raindrop's PropelAuth-backed authorization server (used for MCP OAuth 2.1 and dashboard sign-in). The ingest and query REST APIs use bearer API keys rather than OAuth scopes.

📄 Provider scope reference: https://www.raindrop.ai/docs/mcp/overview

Source

OAuth Scopes

raindrop-scopes.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://auth.raindrop.ai/.well-known/openid-configuration
flow: authorization_code
issuer: https://auth.raindrop.ai
docs: https://www.raindrop.ai/docs/mcp/overview
note: >-
  OAuth/OIDC scopes advertised by Raindrop's PropelAuth-backed authorization
  server (used for MCP OAuth 2.1 and dashboard sign-in). The ingest and query
  REST APIs use bearer API keys rather than OAuth scopes.
scopes:
- name: openid
  description: Standard OpenID Connect scope; returns an ID token.
- name: email
  description: Access to the user's email address and verification status.
- name: profile
  description: Access to basic profile claims (first_name, last_name, picture_url).