granola-local-dev-loop
Access Granola meeting data programmatically for developer workflows. Use when reading notes from the local cache, building MCP integrations, extracting action items into code, or syncing meeting outcomes to dev tools. Trigger: "granola dev workflow", "granola MCP", "granola local cache", "granola developer", "granola programmatic".
Best use case
granola-local-dev-loop is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Access Granola meeting data programmatically for developer workflows. Use when reading notes from the local cache, building MCP integrations, extracting action items into code, or syncing meeting outcomes to dev tools. Trigger: "granola dev workflow", "granola MCP", "granola local cache", "granola developer", "granola programmatic".
Teams using granola-local-dev-loop should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/granola-local-dev-loop/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How granola-local-dev-loop Compares
| Feature / Agent | granola-local-dev-loop | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Access Granola meeting data programmatically for developer workflows. Use when reading notes from the local cache, building MCP integrations, extracting action items into code, or syncing meeting outcomes to dev tools. Trigger: "granola dev workflow", "granola MCP", "granola local cache", "granola developer", "granola programmatic".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# 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.get("meetingsMetadata", {}),
}
cache = load_granola_cache()
docs = cache["documents"]
print(f"Found {len(docs)} meetings in local cache")
# List recent meetings
for doc_id, doc in sorted(docs.items(),
key=lambda x: x[1].get("updated_at", ""),
reverse=True)[:10]:
print(f" {doc.get('title', 'Untitled')} — {doc.get('updated_at', 'N/A')}")
```
### Step 2 — Set Up Granola MCP Server
Granola's official MCP integration connects meeting context to AI tools:
```json
// claude_desktop_config.json or .mcp.json
{
"mcpServers": {
"granola": {
"command": "npx",
"args": ["-y", "granola-mcp-server"]
}
}
}
```
With MCP connected, Claude Code and Cursor can:
- Search across all your meetings by topic or person
- Pull context from specific meetings into coding sessions
- Create tickets based on discussed bugs or features
- Scaffold code based on architectural decisions from meetings
Community MCP servers with additional features:
- `pedramamini/GranolaMCP` — CLI + programmatic + MCP access, reads local cache
- `mishkinf/granola-mcp` — semantic search with LanceDB vector embeddings
- `proofgeist/granola-mcp-server` — lightweight local cache reader
### Step 3 — Extract Action Items to Dev Tools
```python
#!/usr/bin/env python3
"""Extract action items from Granola notes and create GitHub issues."""
import json, re, subprocess
from pathlib import Path
def extract_action_items(note_content: str) -> list[dict]:
"""Parse action items from enhanced Granola notes."""
items = []
# Matches: - [ ] @person: task description
pattern = r'- \[ \] @?(\w+):?\s+(.+)'
for match in re.finditer(pattern, note_content):
items.append({
"assignee": match.group(1),
"task": match.group(2).strip(),
})
return items
def create_github_issue(repo: str, title: str, body: str, assignee: str):
"""Create a GitHub issue using gh CLI."""
cmd = [
"gh", "issue", "create",
"--repo", repo,
"--title", title,
"--body", body,
"--assignee", assignee,
]
result = subprocess.run(cmd, capture_output=True, text=True)
if result.returncode == 0:
print(f" Created: {result.stdout.strip()}")
else:
print(f" Error: {result.stderr.strip()}")
# Usage with cache data
cache = load_granola_cache() # from Step 1
for doc_id, doc in cache["documents"].items():
content = doc.get("last_viewed_panel", {})
# ProseMirror content needs text extraction
text = json.dumps(content) # simplified — parse nodes for production
actions = extract_action_items(text)
for action in actions:
print(f"[{action['assignee']}] {action['task']}")
```
### Step 4 — Sync Meeting Outcomes to Project Docs
```bash
#!/bin/bash
set -euo pipefail
# Sync latest Granola meeting notes to project documentation
NOTES_DIR="$HOME/dev/meeting-notes"
mkdir -p "$NOTES_DIR"
# Extract recent meeting titles and dates using Python
python3 -c "
import json
from pathlib import Path
cache_path = Path.home() / 'Library/Application Support/Granola/cache-v3.json'
if cache_path.exists():
raw = json.loads(cache_path.read_text())
state = json.loads(raw) if isinstance(raw, str) else raw
data = state.get('state', state)
docs = data.get('documents', {})
for doc_id, doc in sorted(docs.items(),
key=lambda x: x[1].get('updated_at', ''),
reverse=True)[:5]:
title = doc.get('title', 'Untitled').replace(' ', '-').lower()
date = doc.get('created_at', 'unknown')[:10]
print(f'{date}_{title}')
"
```
### Step 5 — Git Integration Pattern
Reference Granola meetings in commits and PRs:
```bash
# Reference meeting in commit message
git commit -m "feat: implement user onboarding flow
Per meeting 2026-03-22 'Sprint Planning Q1':
- Agreed on 3-step wizard approach
- Sarah approved the design mockups
- Due by April 15
Action items from Granola note: [link]"
```
## Output
- Local cache accessible for offline meeting data reads
- MCP server connected for AI-assisted meeting context
- Action item extraction pipeline ready
- Meeting-to-dev-tools sync established
## Error Handling
| Error | Cause | Fix |
|-------|-------|-----|
| Cache file not found | Granola not installed or never launched | Install Granola and capture at least one meeting |
| JSON parse error | Double-JSON structure not handled | Parse the outer string first, then parse the inner object |
| MCP server not connecting | Wrong config path | Verify `claude_desktop_config.json` location for your OS |
| Empty transcripts | Transcript stored separately from document | Check `cache["transcripts"]` keyed by document ID |
| Stale cache data | Cache not refreshed | Restart Granola to force cache update |
## Resources
- [Granola MCP Announcement](https://www.granola.ai/blog/granola-mcp)
- [GranolaMCP (cache-based)](https://github.com/pedramamini/GranolaMCP)
- [Reverse-Engineered API Docs](https://github.com/getprobo/reverse-engineering-granola-api)
- [Granola Enterprise API](https://docs.granola.ai/introduction)
## Next Steps
Proceed to `granola-sdk-patterns` for Zapier automation workflows.Related Skills
workhuman-local-dev-loop
Workhuman local dev loop for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman local dev loop".
wispr-local-dev-loop
Wispr Flow local dev loop for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr local dev loop".
windsurf-local-dev-loop
Configure Windsurf local development workflow with Cascade, Previews, and terminal integration. Use when setting up a development environment, configuring Turbo mode, or establishing a fast iteration cycle with Windsurf AI. Trigger with phrases like "windsurf dev setup", "windsurf local development", "windsurf dev environment", "windsurf workflow", "develop with windsurf".
webflow-local-dev-loop
Configure a Webflow local development workflow with TypeScript, hot reload, mocked API tests, and webhook tunneling via ngrok. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with the Webflow Data API. Trigger with phrases like "webflow dev setup", "webflow local development", "webflow dev environment", "develop with webflow".
vercel-local-dev-loop
Configure Vercel local development with vercel dev, environment variables, and hot reload. Use when setting up a development environment, testing serverless functions locally, or establishing a fast iteration cycle with Vercel. Trigger with phrases like "vercel dev setup", "vercel local development", "vercel dev environment", "develop with vercel locally".
veeva-local-dev-loop
Veeva Vault local dev loop for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva local dev loop".
vastai-local-dev-loop
Configure Vast.ai local development with testing and fast iteration. Use when setting up a development environment, testing instance provisioning, or building a fast iteration cycle for GPU workloads. Trigger with phrases like "vastai dev setup", "vastai local development", "vastai dev environment", "develop with vastai".
twinmind-local-dev-loop
Set up local development workflow with TwinMind API integration. Use when building applications that integrate TwinMind transcription, testing API calls locally, or developing meeting automation tools. Trigger with phrases like "twinmind dev setup", "twinmind local development", "twinmind API testing", "build with twinmind".
together-local-dev-loop
Together AI local dev loop for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together local dev loop".
techsmith-local-dev-loop
TechSmith local dev loop for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith local dev loop".
supabase-local-dev-loop
Configure Supabase local development with the CLI, Docker, and migration workflow. Use when initializing a Supabase project locally, starting the local stack, writing migrations, seeding data, or iterating on schema changes. Trigger with phrases like "supabase local dev", "supabase start", "supabase init", "supabase db reset", "supabase local setup".
stackblitz-local-dev-loop
Configure local development for WebContainer applications with hot reload and testing. Use when building browser-based IDEs, testing WebContainer file operations, or setting up development workflows for WebContainer projects. Trigger: "stackblitz dev setup", "webcontainer local", "test webcontainers locally".