Fireflies.ai · Authentication Profile
Fireflies Authentication
Authentication
Fireflies runs TWO distinct authentication models on the same product, and conflating them is the common integration mistake. The GraphQL API is a long-lived bearer API key with no OAuth and no scopes. The hosted MCP server is a full OAuth 2.0 authorization server with PKCE, dynamic client registration and revocation — but only two identity scopes. Upgraded from the previous derived profile, which saw only the OpenAPI BearerAuth scheme.
Fireflies.ai secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
Artificial IntelligenceMeeting AssistantTranscriptionSummaryAction ItemsGraphQLMeetingsProductivityCollaborationConversation Intelligence
Methods: http, oauth2
Schemes: 2
OAuth flows: authorizationCode
API key in: header
Security Schemes
BearerAuth http
FirefliesMCPOAuth oauth2
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.