meeting-sync

Granola meeting notes sync into a local knowledge base by checking for unsynced meetings through Granola MCP tools, letting you select specific sessions, and writing transcript files to a local Knowledge folder. The process tracks sync state in a local JSON file to avoid duplicates.

Making Granola transcripts actionable for morning planning involves syncing new meeting notes into a local Knowledge/Transcripts folder so your daily tasks and follow-ups are grounded in the freshest context. You can choose to sync only meetings containing actual notes.

Granola MCP integration is required to sync meeting transcripts locally because the process relies on calling Granola MCP tools to check for unsynced meetings, retrieve meeting IDs, and fetch content for writing into your local knowledge structure.

You can choose which Granola meetings to sync through a guided selection flow that presents unsynced meetings and lets you sync all new meetings, select specific ones individually, or skip syncing entirely for that session.

Granola meeting notes may not show up in your local Knowledge folder if the sync state file tracks them as already processed, if no unsynced meetings were detected by the MCP check, or if you skipped the selection flow during your last sync session.

Meeting-sync works for reviewing past decisions and action items by storing Granola meeting content in sanitized local transcript files, making historical meeting data immediately available for your AI assistant to parse during task follow-up reviews.