granola-saver 1.1.0

Your Granola meeting transcripts, saved locally. Automatically.

granola-saver

Your Granola meeting transcripts, saved locally. Automatically.

Granola transcribes your meetings beautifully - but transcripts live in a local cache that evicts after a few meetings. If you're on the free plan, notes older than 30 days disappear from the app entirely.

granola-saver watches for new meetings and saves each transcript as a clean markdown file the moment it ends. No cloud dependency, no API keys, no paid plan required.

Use with Claude Desktop

Add to your config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "granola-saver": {
      "command": "uvx",
      "args": ["granola-saver"]
    }
  }
}

Restart Claude Desktop. Then ask Claude about your meetings:

• "What meetings did I have this week?"
• "Show me the transcript from my call with Sarah"
• "Search my meetings for anything about the product launch"
• "Export yesterday's standup to a file"

Available Tools

Tool	What it does
list_meetings	Browse recent meetings with metadata
get_transcript	Read a full meeting transcript
search_meetings	Search by title, attendee, or keyword
export_meeting	Save a transcript as a markdown file
get_status	Check cache and daemon status

Optional: Auto-Export Daemon

The MCP server gives you on-demand access through Claude. If you also want every meeting saved automatically as it ends, install the background daemon:

git clone https://github.com/adampaulwalker/granola-saver.git
cd granola-saver
bash install.sh

The installer will:

• Ask where you'd like transcripts saved (default: ~/Granola Transcripts)
• Set up a background daemon that starts automatically on login
• Every meeting gets saved as a dated markdown file within 60 seconds of ending

Daemon Commands

# Check if the daemon is running
launchctl list | grep granola-saver

# View live logs
tail -f daemon.log

# Uninstall
bash uninstall.sh

Advanced: Folder Routing

Route transcripts to different folders based on attendee email domains or meeting title keywords. Edit routing-map.json:

{
  "email_domains": {
    "acme.com": "Acme Corp",
    "bigclient.io": "Big Client"
  },
  "title_keywords": {
    "standup": "Team/Standups",
    "interview": "Hiring"
  },
  "default_folder": ""
}

How it works

1. Granola writes meeting data to a local cache file on your Mac
2. granola-saver reads this cache to serve meeting data via MCP
3. The optional daemon watches for changes using macOS native file events
4. When a meeting ends, the transcript is extracted and saved as a dated markdown file

What you get

Every meeting saved as 2026-03-13-meeting-title.md with:

• YAML frontmatter (title, date, duration, attendees)
• Granola's AI-generated notes (if available)
• Full timestamped transcript

Requirements

• macOS (Granola's cache is macOS-only)
• Python 3.10+
• Granola (any plan, including free)

How is this different from Granola's MCP?

Granola's official MCP lets you query your meetings from AI tools. That's great for on-demand access, but it doesn't save anything locally.

granola-saver does both:

• MCP server: Query your meetings from Claude Desktop (same as Granola's MCP)
• Auto-export daemon: Saves every transcript as a local markdown file the moment your meeting ends (Granola doesn't do this)

Your transcripts live as plain files on your machine that you can search, back up, sync, or process however you want.

License

MIT