Give Claude your meeting memory
MeetingVault transcribes every meeting on your Mac using on-device Whisper. The MCP server exposes those transcripts to Claude Desktop. Your AI can now reason over your actual meetings. Nothing leaves your machine.
Claude Desktop, with MeetingVault MCP
What did we decide in the product review meeting last Tuesday?
In your product review on March 18th, you decided to delay the onboarding redesign until after the v1.0 launch. The main concern raised by Sarah was that the current flow works well enough for beta users and a redesign mid-cycle creates risk. You also agreed to ship the search feature by end of quarter. Want me to pull the action items from that meeting?
Yes, and check if we ever followed up on the API rate limit issue from Q4
Action items from March 18th: [1] Ship search feature by March 31 (owner: Dev team) [2] Revisit onboarding redesign after v1.0 launch...
On the API rate limit: it came up in your Nov 12 engineering sync. No follow-up appears in any later transcript. Looks like it slipped.
* Zero network calls. Transcripts never left your Mac.
How it works
MeetingVault records and transcribes on-device
Every meeting gets a local transcript using Whisper. Audio is discarded the moment transcription completes. Only the text stays, on your Mac.
The MCP server runs locally alongside your app
A lightweight server exposes your transcripts through the Model Context Protocol. It reads from the same local database MeetingVault writes to. No sync, no upload, no intermediary.
Claude Desktop connects to it like any MCP tool
Add one block to your claude_desktop_config.json. Claude can now search, summarize, and reason over every meeting you've transcribed.
Setup (when available)
Add this to your Claude Desktop config. That's the entire setup.
Coming soon via Homebrew: brew install LocalFlowApp/tap/meetingvault-mcp
What you can ask Claude
Search across all meetings
"When was the last time we talked about pricing?"
Extract action items
"Pull every commitment I made in Q1 that we haven't shipped yet."
Summarize and compare
"What changed in our thinking about the API between January and March?"
Catch what slipped
"What did we say we'd follow up on that never appeared in a later meeting?"
Prepare for meetings
"Summarize all our investor call transcripts so I can prep for tomorrow."
Draft follow-ups
"Write a follow-up email based on yesterday's client call."
Zero network calls. Always.
The entire stack is local. MeetingVault writes transcripts to a local SQLite database. The MCP server reads from that database and responds to Claude Desktop over a local Unix socket. Nothing touches a server at any point.
You can verify this with Wireshark, Little Snitch, or macOS Network Monitor. We built a step-by-step verification guide if you want to audit it yourself.
Open source MCP server
The MCP server is fully open source. You can read every line before running it. No telemetry, no update checks, no callbacks.
LocalFlowApp/meetingvault-mcpStatus: In active development
The MCP server is being built alongside the core app. Waitlist members get early access. If you're a Claude Desktop user who cares about keeping meeting content private, this is built for you.
Get early access when the MCP server ships
Join the waitlist. We email you when it's ready.
Join the WaitlistNo spam. One email when it's ready.