Fireflies.ai

Fireflies.ai

Let your AI work with your Fireflies.ai meeting notes: find recorded meetings, read AI summaries, action items and transcripts, search what was said, ask AskFred about one or many meetings, and with your confirmation send the notetaker bot into a live call or upload a recording.

7 días gratis · sin tarjeta · hosting UE

Pregunta cualquier cosa a Fireflies.ai

Prueba un prompt real contra Fireflies.ai vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.

Instalar Fireflies.ai en Cloud
Fireflies.ai · live vía MCP
Compartir
Opus 4.7

Claude es IA y puede equivocarse. Verifica siempre las respuestas.

Setup en 2 minutos

  1. 1Inicia trial gratuita en cloud.anythingmcp.com.
  2. 2Click en Fireflies.ai en el connector store. Pega las credenciales.
  3. 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Instalar Fireflies.ai ahora

Guías para Fireflies.ai

Setup paso a paso para los principales clientes AI.

Configurar Fireflies.ai

Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.

Fireflies.ai

This connector works with Fireflies.ai, the AI notetaker, through its public GraphQL API (https://api.fireflies.ai/graphql) with the API key of a Fireflies user: recorded meetings with their AI notes and full text, soundbites, the team and channels, and AskFred, Fireflies' assistant that answers questions about meetings. It can also send the notetaker bot into a running meeting and upload a recording for transcription.

Setup (about 2 minutes)

  1. Sign in at https://app.fireflies.ai and open Integrations, Fireflies API (https://app.fireflies.ai/integrations/custom/fireflies), or Settings, Developer settings.
  2. Copy the API key and paste it into FIREFLIES_API_KEY. It is sent as Authorization: Bearer <key> and only to Fireflies.
  3. Check the setup with fireflies_get_current_user.

The key acts as its owner: the connector sees the meetings that user can see in Fireflies (an admin's key sees the whole team's). Share the MCP server only with people allowed to see those meetings.

Recordings and transcripts are personal data. They hold what colleagues, customers and other participants said, with names and email addresses. Only fetch what the user's question needs, prefer the AI notes and short summaries over the full text, and do not copy transcripts to other systems unless the user asks for it.

How to work

  1. Find meetings: fireflies_list_transcripts (date range, organizers, participants, a team member, a channel, or mine), or fireflies_search_transcripts for a word in titles or in what was said. Both page with limit (up to 50) and skip.
  2. Read one meeting: fireflies_get_transcript for the AI notes (overview, action items, keywords, outline, topics), speakers and attendees. fireflies_get_transcript_text for what was said, 700 lines at a time as [start second, speaker, text]; when totalLines is above 700, fireflies_get_transcript_text_more gives lines 701 to 1400. Fireflies has no further paging; for very long meetings search or ask AskFred.
  3. Ask questions: fireflies_ask_about_meeting (one meeting) or fireflies_ask_across_meetings (filters, default last 30 days), then fireflies_ask_follow_up with the returned threadId. Each AskFred answer uses AI credits of the Fireflies plan: tell the user before the first question of a conversation. Earlier conversations: fireflies_list_askfred_threads, fireflies_get_askfred_thread.
  4. Soundbites: fireflies_list_bites (pass mine, my_team or transcript_id), fireflies_get_bite, and fireflies_create_bite to cut a new clip.
  5. Team: fireflies_get_current_user, fireflies_list_users, fireflies_list_channels. Live: fireflies_list_active_meetings.

Writes: confirm first. fireflies_create_bite and fireflies_upload_audio create content in the account. fireflies_add_bot_to_live_meeting sends the Fireflies bot into a running call, where every participant sees it join and knows the call is recorded: tell the user that, confirm the meeting link and wait for their yes. In some places recording needs everyone's consent; that is the user's responsibility. fireflies_delete_transcript (deletes for good) and fireflies_set_user_role (admin rights) are installed switched off; an admin turns them on deliberately.

Limits: Free plan 30 requests a minute and 500 a day, Pro 60 a minute and 5,000 a day, Business and Enterprise 60 a minute per paid seat for the team. Adding the bot is limited to 3 calls per 20 minutes per user. Audio and video URLs need a Pro plan or higher.

Errors

  • auth_failed (Fireflies answers it with HTTP 500): the API key is wrong or was replaced. Copy it again from Integrations, Fireflies API.
  • object_not_found: wrong id, or the key's user cannot see that meeting.
  • too_many_requests or HTTP 429: the plan's limit is reached; wait for the time in the message.
  • paid_required: the feature (audio or video links, analytics) needs a higher Fireflies plan.
  • forbidden or require_elevated_privilege: the key's user may not do this, for example someone else's meeting without admin rights.
  • require_ai_credits: AskFred has no AI credits left on the plan.

Other operations: fireflies_graphql_query runs any read of the API; Fireflies shows its schema to signed-in requests, so ask for a type with query { __type(name: \"Transcript\") { fields { name } } }. Fireflies publishes no SDL file, so fireflies_graphql_schema cannot load the schema; use that introspection instead. fireflies_graphql_mutation could change or delete anything the key can and is installed switched off, like fireflies_graphql_subscription.

Out of scope here: sharing meetings and changing privacy, titles or channels, user groups, live action items, pausing a recording, analytics, AI app outputs, contacts, the audit log and webhooks.

Tu IA está a dos clicks de Fireflies.ai.

Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.