granola-local-dev-loop

# Granola Local Dev Loop ## Overview Access Granola meeting data programmatically using three methods: the local cache file (zero-auth, offline), the MCP server (AI agent integration), or the Enterprise API (workspace-wide access). Build developer workflows that turn meeting outcomes into code tasks, documentation, and project artifacts. ## Prerequisites - Granola installed with meetings captured - Node.js 18+ or Python 3.10+ for scripts - For MCP: Claude Code, Cursor, or another MCP-compatible client - For Enterprise API: Business/Enterprise plan + API key ## Instructions ### Step 1 — Read the Local Cache (Zero Auth) Granola stores meeting data in a local JSON cache file: ```bash # macOS cache location CACHE_FILE="$HOME/Library/Application Support/Granola/cache-v3.json" # Check if cache exists and get size ls -lh "$CACHE_FILE" ``` The cache has a double-JSON structure (JSON string inside JSON): ```python #!/usr/bin/env python3 """Extract meetings from Granola local cache.""" import json from pathlib import Path CACHE_PATH = Path.home() / "Library/Application Support/Granola/cache-v3.json" def load_granola_cache(): raw = json.loads(CACHE_PATH.read_text()) # Cache contains a JSON string that needs secondary parsing state = json.loads(raw) if isinstance(raw, str) else raw data = state.get("state", state) return { "documents": data.get("documents", {}), "transcripts": data.get("transcripts", {}), "meetings_metadata": data.ge...