Connect your meetings to Claude β or any AI you trust.
MeetMemo speaks MCP, the open protocol Claude Desktop and Cursor use to read from local tools. Your transcripts stay on your Mac.
What is MCP?
MCP (Model Context Protocol) is an open spec by Anthropic. It lets AI clients β like Claude Desktop and Cursor β read from local tools you control. MeetMemo runs a small MCP server on your Mac. When you ask Claude a question, Claude can pull relevant meeting transcripts to ground its answer. Nothing leaves your Mac unless you ask Claude something β and even then, only the snippets Claude needs.
What MeetMemo's MCP server exposes
Eight focused tools and an attachable resource URI β no surprises.
search_meetingsHybrid BM25 + vector search across every transcript on your Mac. Filterable by date range and theme.
get_transcriptFull transcript for a meeting, in markdown or structured JSON.
get_transcript_textPlain-text transcript for fast context attachment.
find_relatedMeetings similar to a given one, ranked by similarity.
list_action_itemsAction items extracted across a date range or per person.
get_context_for_dateEverything you talked about on a given day.
summarize_meetingOn-device structured summary for a single meeting.
synthesizeCross-meeting synthesis with citation extraction.
Setup in 60 seconds
Claude Desktop
- 1
Open MeetMemo β Settings β Connect AI
Find the MCP panel in MeetMemo's settings.
- 2
Click "Connect Claude Desktop"
MeetMemo writes the config for you after a confirmation.
- 3
Restart Claude Desktop
The MeetMemo tools appear in Claude's tool menu.
{
"mcpServers": {
"meetmemo": {
"command": "/Applications/MeetMemo.app/Contents/MacOS/MeetMemo",
"args": ["--mcp-stdio"]
}
}
}Cursor
- 1
Open MeetMemo β Settings β Connect AI
Find the MCP panel in MeetMemo's settings.
- 2
Click "Connect Cursor"
MeetMemo writes ~/.cursor/mcp.json for you after a confirmation.
- 3
Restart Cursor
MeetMemo's tools become available to Cursor's agent.
{
"mcpServers": {
"meetmemo": {
"command": "/Applications/MeetMemo.app/Contents/MacOS/MeetMemo",
"args": ["--mcp-stdio"]
}
}
}Other clients
Any MCP-compatible client works. Point it to MeetMemo's stdio entry point or to the local socket at ~/Library/Application Support/MeetMemo/mcp.sock.
Privacy and audit, by default
- MCP server binds to a local Unix socket. No network exposure, ever.
- Every tool call is logged in MeetMemo's audit trail β see exactly what Claude asked.
- Disable MCP with one toggle. The socket is removed within a second.
Try these in Claude
βWhat did we decide about pricing in the last two months?β
βSummarize action items assigned to Maria this quarter.β
βFind meetings related to the API migration.β
βWhat was said on April 14, 2026?β
FAQ
Does Claude store my meeting data after a query?
No β Claude only sees the snippets needed for your question. MeetMemo never sends your full library, and Claude's normal data policies apply to the snippets returned.
Do I need a paid Claude plan?
Any Claude Desktop installation that supports MCP works. Free or paid.
Can I disable specific tools?
Yes β Settings β Connect AI lets you toggle each tool individually.
What about Cursor users?
Cursor's MCP support is first-class. Same one-click setup.
Ready to connect your meetings?
MeetMemo speaks MCP, the open protocol Claude Desktop and Cursor use to read from local tools. Your transcripts stay on your Mac.