[Day 6 of 30] Connect Your Meeting Tracker to PKM via MCP
Meeting transcripts pile up in the app. Connect them to your vault so person pages, action items, and context land in your knowledge base.
The situation
You record meetings with an AI note-taker. Transcripts pile up. But they never flow into your knowledge base. Person pages stay empty. Action items stay in the app. Your vault or second brain has no meeting context. On Days 3 and 4 you connected calendar and email. To have meeting content as well, you add a meeting tracker next.
This post continues the 1% Better series; if you have not read the first five posts, you can find them here.
The 1% upgrade
To get meeting context into your vault, connect your meeting tracker via MCP (Model Context Protocol). MCP bridges the tracker to your PKM. Your PKM reads meetings and writes structured notes, person pages, and action items into your vault. The whole system is interconnected so that meeting context lands directly in your knowledge system.
Which trackers have MCP
I checked the current landscape. Here are the ones with real integrations you can use:
Granola (recommended). Privacy-focused, bot-free capture from any desktop audio. Official MCP works with meeting transcripts and notes. Works with Cursor and Claude Code.
You can:
Search meetings by criteria
List your meetings
Get details for one or more meetings
Get the full transcript (paid tiers only)
Free plan includes notes from last 30 days only.
Fireflies. Popular for teams, good for Zoom/Meet/Teams. Official MCP in beta. Strong for sales analysis, product research, and tracking decisions across meetings. Works with Cursor and Claude Code.
Fathom. Generous free tier, Zoom/Meet/Teams. Community MCP only (no official server yet).
Where to get it: GitHub: matthewbergvinson/fathom-mcp
You can:
List your meetings
Search meetings by criteria
Get the full transcript
Get a meeting summary
Less polished than official offerings, but usable.
Other tools (Otter, Fellow, Notta, etc.) also have their own MCPs. You can connect them the same way as the tools I describe in this article. For this post, we stick to Granola, Fireflies, and Fathom.
How to add the meeting tracker MCP
Each tracker has its own setup. Use the one that matches your app.
Granola
You need a Granola account with meeting notes.
Add the MCP to your app.
In Cursor (MCP config):
In a new chat, ask: “Add the Granola MCP to my MCP config.” The AI will create or update your config.
Restart Cursor so it loads the new server.
In Claude Code (Connectors):
Open Settings, then Connectors.
Search for Granola and turn the connector on.
First sign-in.
Turn the Granola server on in Tools and MCP (Cursor) or Connectors (Claude Code).
In a new chat, ask: “List my last 5 meetings.”
A browser opens for OAuth sign-in. Sign in once; the token is saved.
Use it.
Ask: “Pull my last 3 meetings from Granola, extract action items and update person pages.” The AI reads via MCP and writes into your PKM.
Fireflies
You need a Fireflies account. The MCP is in beta; enable it from your Fireflies account first, then add the server.
Add the MCP to your app.
In Cursor: In a new chat, ask: “Add the Fireflies MCP to my MCP config.” Restart Cursor after the AI updates the config.
In Claude Code: Settings -> Connectors -> search Fireflies -> connect.
First sign-in. Turn the server on, then in a new chat ask: “List my last 5 meetings.” Complete OAuth in the browser when prompted.
Use it. Same flows as Granola: list meetings, get transcripts, extract action items into your vault.
Fathom
Fathom has a community MCP only (no official server).
Add the MCP to your app (Cursor or Claude Code).
In a new chat, ask: “Add the Fathom MCP to my MCP config. Community server: GitHub matthewbergvinson/fathom-mcp.” Restart the app after the AI updates the config.
First sign-in. Turn the Fathom server on, then ask: “List my last 5 meetings.” Sign in when the browser opens.
Use it. List meetings, search, get transcript or summary. Pipe results into your vault.
Takeaway
With a meeting tracker MCP (Granola, Fireflies, or Fathom) connected, your AI reads transcripts and writes structured content into your vault. Person pages, action items, and meeting context flow into your knowledge base. No more copy-pasting.
10-minute action
Pick your tracker (Granola, Fireflies, or Fathom) and connect the MCP using the instructions above.
Run one flow: ask your AI to pull your last 3 meetings and write notes, action items, and person context into your vault.
Outcome: meeting content lands in your vault, not only stays in the app.
Confirm that meeting notes or action items have landed in your vault or task system. From here you can: prep for the next meeting with the same people (context is already on their person page), run triage or daily planning on the new tasks, and search your vault when you need to recall what was decided.
Capturing habit (this week). We’re practicing the Capturing Skill as a habit this week. When you pull meetings into your vault, make sure everything gets captured: person pages, action items, context.
How: explicitly ask the AI to write to files (e.g. create notes in Inbox, update person pages in People/, add tasks to your task list). Don’t let useful output stay only in the chat reply.
Example: “Pull my last 3 meetings. For each: create a note in 00-Inbox/, update or create person pages in People/, and add action items to my task list. Save everything to my vault.”
You can also turn transcripts into a task list.
Prompt: “Pull my last 3 meetings from [Granola/Fireflies/Fathom]. Extract all action items and decisions with owners. Create a task list and save it to my task system (or to 03-Tasks/Tasks.md). Each task: clear verb, owner if known, source meeting.”
What to do next
Before your next recurring meeting (standup, 1:1, project sync), ask your AI:
“Prep me for my meeting with [name]. Pull our last 2–3 meetings from [tracker], summarize what we discussed and what’s still open, and show me their person page.”
You’ll see how meeting context compounds: each captured session makes the next prep sharper. Try it once and see the difference.