Granola released their official MCP—you should 100% just use that. This was built prior to that release.

Granola Export

Export your Granola meeting transcripts to local JSON files, optimized for AI querying and search.

Features

• Automatic export — Transcripts are exported automatically when meetings end
• Incremental sync — Only exports new transcripts, skips already-exported ones
• AI-optimized format — JSON structure designed for easy AI/LLM consumption
• Searchable index — Master index file for quick lookups across all meetings
• Manual export — Click the app anytime to export on-demand
• Cloud sync — Optionally push exports to GitHub or custom destination

What Gets Exported

Each meeting is saved as a JSON file containing:

{
  "id": "meeting-uuid",
  "title": "Weekly Team Sync",
  "date": "2024-01-15T10:00:00.000Z",
  "people": ["Alice", "Bob"],
  "summary": "AI-generated meeting summary...",
  "notes_markdown": "Your notes in markdown...",
  "transcript_text": "Full conversation with speaker labels...",
  "transcript_segments": [
    {
      "speaker": "Alice",
      "text": "Let's get started...",
      "start": 0,
      "end": 2500
    }
  ]
}

Requirements

• macOS 10.15+
• Granola installed
• Python 3 (included with macOS)

Installation

git clone https://github.com/rileycx/granola-export.git
cd granola-export
./install.sh

The installer will:

1. Create ~/granola-export/ directory
2. Set up automatic export (triggers when Granola saves a meeting)
3. Create a macOS app for manual exports
4. Run an initial export of all cached transcripts

Usage

Automatic Export

After installation, transcripts are exported automatically whenever you finish a Granola meeting. No action needed.

Manual Export

Double-click GranolaExport.app in ~/granola-export/ or add it to your Dock.

Command Line

python3 ~/granola-export/export_granola.py

For terminal-first usage:

# Custom export directory + machine-readable summary
python3 ~/granola-export/export_granola.py --export-dir ~/granola-export --json

# Use a custom cache path and skip sync
python3 ~/granola-export/export_granola.py --cache-path "/path/to/cache-v3.json" --no-sync

Run python3 ~/granola-export/export_granola.py -h for all options.

Export Location

~/granola-export/
├── index.json              # Searchable index of all meetings
├── export.log              # Export history and errors
├── GranolaExport.app       # Click to export manually
└── meetings/
    ├── 2024-01-15_weekly-team-sync_abc12345.json
    ├── 2024-01-14_product-review_def67890.json
    └── ...

Querying with AI

The export format is optimized for AI assistants. Example prompts:

• "Search my meetings for discussions about pricing"
• "Summarize what Alice said in last week's meetings"
• "Find all action items from January meetings"

Load the index.json for quick lookups, or individual meeting files for full transcripts.

Cloud Sync (Optional)

Automatically sync your exports to a remote destination after each export. Useful for:

• Backing up transcripts
• Sharing with AI tools that can access GitHub/cloud storage
• Syncing across machines

Setup During Install

The installer will ask if you want to enable cloud sync. You can also configure it manually later.

GitHub Sync

Push exports to a private GitHub repo:

1. Create a private repo on GitHub (e.g., my-granola-transcripts)

2. Edit ~/.granola-export-config.json:

{
  "sync_enabled": true,
  "sync_method": "github",
  "github_repo": "yourusername/my-granola-transcripts",
  "github_branch": "main"
}

3. Initialize git in your export folder:

cd ~/granola-export
git init
git remote add origin git@github.com:yourusername/my-granola-transcripts.git
git add -A
git commit -m "Initial export"
git push -u origin main

After setup, exports will auto-push to GitHub. If the git origin remote does not match github_repo, sync will be skipped with a warning.

Custom Command Sync

Run any shell command after each export (rsync, S3, etc.):

{
  "sync_enabled": true,
  "sync_method": "command",
  "sync_command": "rsync -av meetings/ user@server:/backups/granola/",
  "sync_on_no_new": false
}

Set sync_on_no_new to true if you want the command to run even when no new meetings were exported (e.g., to capture index.json updates).

More examples:

# AWS S3
"sync_command": "aws s3 sync meetings/ s3://my-bucket/granola/"

# rclone (Dropbox, Google Drive, etc.)
"sync_command": "rclone sync meetings/ dropbox:granola-exports"

# Simple copy to another folder
"sync_command": "cp -r meetings/ /Volumes/Backup/granola/"

Disable Sync

Set sync_enabled to false in the config file:

{
  "sync_enabled": false
}

Sync Logs

Sync results are logged to ~/granola-export/export.log.

Important Notes

Granola only caches recent transcripts locally. To export older meetings:

1. Open the meeting in Granola (this caches the transcript)
2. Run the export (automatic or manual)

The exporter reads from Granola's local cache at:

~/Library/Application Support/Granola/cache-v3.json

Uninstall

cd granola-export
./uninstall.sh

Your exported meetings in ~/granola-export/meetings/ will be preserved.

License

MIT License - see LICENSE

Credits

Built for the Granola community. Not affiliated with Granola.