Fireflies logo

Connect Fireflies to Town

Reply drafts, meeting prep, and answers pulled from every call your team records. One click through Fireflies' official MCP server. Nothing to install.

Connect Fireflies

Free to start

Flip the dog Townie waving in a striped shirt

Flip found the answer in a teammate's call and drafted your reply.

See it work: a routine built on your Fireflies meetings

Draft my replies with the team's call history

Set it up once. Hit send when ready.

How to connect the Fireflies MCP to Town

  1. Open Integrations in Town

    Go to Integrations in your Town workspace (free to create) and find Fireflies.

  2. Authorize the connection

    Sign in to Fireflies when prompted. Town connects through Fireflies' official MCP server (api.fireflies.ai), so there's nothing to install or configure — and the connection is read-only.

  3. Ask about any meeting

    Done — your Townie can now search every call your Fireflies account can see, yours and your teammates', and use them in routines.

Just ask your Townie

Fireflies remembers every call your team takes. Town puts that memory to work in your inbox, docs, and to-do list.

  • “When did anyone last meet with Quartz?”

    Every call across the team, answered in seconds.

  • “Grab the pricing clip from Tuesday's demo.”

    Your Townie finds the soundbite and drops it in a Slack draft.

  • “How much time were we in meetings this month?”

    Fireflies analytics, written up in Town's editor.

Fireflies integration FAQ

The Fireflies MCP is Fireflies' hosted Model Context Protocol server at api.fireflies.ai/mcp — the official integration surface Fireflies maintains. MCP is the open standard that lets AI assistants securely search and read data from apps — in this case your team's Fireflies meetings: transcripts, summaries, soundbites, channels, and analytics. Town connects to it in one click; no API keys or local setup.

Town only reads Fireflies data when you (or a routine you configured) ask for it, and access is scoped to your Fireflies account — Town sees the meetings you can see, nothing more. Anything Town drafts from them — emails, updates, docs — waits for your approval. Read more about how Town approaches security.

No — every Fireflies tool Town uses is read-only. Recording, notetaking, channels, and soundbites stay in Fireflies. Town acts on the meetings elsewhere: drafted replies, briefs, to-dos, and docs.

The meetings your Fireflies account can see — including teammates' calls, when your workspace shares them. Under the hood these are Fireflies' MCP tools: search meetings, search transcripts, get transcript, get summary, get soundbites, list channels, get contacts, and meeting analytics.

You need a Fireflies account with recorded meetings, and a Town account — free to start. The Fireflies connection works on every Town plan. A few tools mirror Fireflies plan features — automation-rule logs, for example, require Fireflies Enterprise.

Fireflies is an AI notetaker that records, transcribes, and organizes your team's meetings — the shared archive of everything said on every call. Town is an AI assistant that acts on your work: email, calendar, docs, to-dos. Connected, the archive gets hands — replies cite the call, briefs include the history, and action items land on your list.

What is Fireflies?

Fireflies.ai is an AI notetaker that joins your team's meetings, records and transcribes them, and organizes everything into searchable channels and soundbites — a shared memory of every call anyone on the team has taken.

Fireflies keeps the record; Town puts it to work. Connect the two and any meeting anyone recorded becomes context your assistant can act on — across your inbox, calendar, documents, and to-do list.

Visit fireflies.ai

Meet your

Bo the bear Townie

bo@town.com

today.