Can AI agents automate Fireflies?

Fireflies is automatable today through the official remote MCP at https://api.fireflies.ai/mcp and through the GraphQL API at https://api.fireflies.ai/graphql. This record is Fireflies.ai meeting recording, transcripts, summaries, soundbites, channels, and users. It is not Zoom, Microsoft Teams, or Otter. The GraphQL API authenticates with Authorization: Bearer and an API key from the Fireflies dashboard. Queries cover transcripts, users, channels, bites, analytics, and related meeting data. Opened mutations include uploadAudio, deleteTranscript, and shareMeeting. The API does not support Super Summary or Custom Apps data. Free-plan API use is 50 requests per day; Pro is 500 per day; Business and Enterprise are 60 requests per minute. uploadAudio requires a paid plan. Webhooks V2 POST meeting.transcribed, meeting.summarized, and meeting.bot_joined events, with optional HMAC-SHA256 signatures. The hosted MCP uses OAuth or a Bearer API key. The opened tools catalog documents search, transcript, summary, sharing, channel, soundbite, user, analytics, and Enterprise rule-execution tools. fireflies_search and fireflies_fetch are marked experimental. A separate documentation MCP at https://docs.fireflies.ai/mcp searches docs only and is not the meeting-data server. An official SDK and CLI were not established on the opened pages. iPaaS connector catalogs were not opened. Computer-use viability is unassessed. MCP scores 8 and is the best path for agents. The GraphQL API scores 7 because of plan-gated rate limits, paid upload, and the Super Summary gap.

Best path today: mcp · Overall automatability: 8/10