Doctor Droid · Authentication Profile

Doctor Droid Authentication

Authentication

Doctor Droid secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyAiAIOpsSREIncident ResponseOn-CallObservabilityDevOpsMonitoringMCP
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

doctor-droid-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://docs.drdroid.io/getting-started/drdroid-mcp-server
docs: https://docs.drdroid.io/getting-started/drdroid-mcp-server
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_generation: Dashboard > Settings > Proxy Tokens, API Keys & MCP
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    DrDroid platform and MCP access is authenticated with a Bearer API key passed in the Authorization
    header. Keys are generated in the DrDroid dashboard under Settings > Proxy Tokens, API Keys & MCP.
  in: header
  header: Authorization
  sources: [https://docs.drdroid.io/getting-started/drdroid-mcp-server]
notes: >-
  The DrDroid trust center at security.drdroid.io separately exposes an OAuth 2.0 authorization-server
  (SafeBase-hosted, PKCE S256, authorization_code + refresh_token) for its own MCP endpoint — see
  well-known/doctor-droid-oauth-authorization-server.json. That is distinct from DrDroid platform auth,
  which is the Bearer API key documented above.