zoom-summaries
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zoom-summaries write the summary for meeting 96980348286 to my Obsidian note"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zoom Meeting Summaries MCP Server
An MCP (Model Context Protocol) server that provides access to Zoom meeting summaries and writes them into an Obsidian vault. Uses Puppeteer-based browser authentication — on first use, a browser window opens for you to sign in to Zoom. Session cookies are saved to ~/.zoom-mcp/cookies.json and reused automatically until they expire.
Configurable for any Zoom organization (e.g., acme.zoom.us, yourcompany.zoom.us).
Prerequisites
Node.js 18+
A Zoom account with AI Companion meeting summaries enabled
An Obsidian vault with 1:1 note files named
First Last.md
Related MCP server: academic-workflow-mcp
Setup
npm install
npm run buildConfiguration
Variable | Description | Default |
| Your org's Zoom vanity subdomain (e.g. | (empty — uses zoom.us) |
| Absolute path to your Obsidian vault root | (required) |
| Subfolder within the vault containing 1:1 note folders (e.g. | (empty — search directly under vault root) |
| Comma-separated list of folder names holding 1:1 notes |
|
| (Optional, v1.1.0+) Folder for meetings shared WITH you. If not set, shared meetings are not processed. | (empty) |
Usage with Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"zoom-summaries": {
"command": "node",
"args": ["/absolute/path/to/zoomFetchMCP/build/index.js"],
"env": {
"ZOOM_SUBDOMAIN": "acme",
"OBSIDIAN_VAULT_PATH": "/path/to/your/vault",
"VAULT_SUBFOLDER": "MyOrg",
"ONE_ON_ONE_FOLDERS": "! One on Ones,! One on Ones (Other)"
}
}
}
}Usage with VS Code Copilot (Agent Mode)
Ensure chat.agent.enabled is turned on in VS Code settings. Then add .vscode/mcp.json to your workspace:
{
"servers": {
"zoom-summaries": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/zoomFetchMCP/build/index.js"],
"env": {
"ZOOM_SUBDOMAIN": "acme",
"OBSIDIAN_VAULT_PATH": "/path/to/your/vault",
"VAULT_SUBFOLDER": "MyOrg",
"ONE_ON_ONE_FOLDERS": "! One on Ones,! One on Ones (Other)"
}
}
}
}Available Tools
zoom_login
Opens a browser window for you to sign into Zoom. Call this first if you get authentication errors. Session cookies are saved to ~/.zoom-mcp/cookies.json for automatic reuse.
list_meeting_summaries
List meeting summaries with optional source and date filtering.
Parameter | Type | Description |
| string (optional) |
|
| string (optional) | Start date (e.g. |
| string (optional) | End date (e.g. |
get_meeting_summary
Get the full AI-generated summary for a specific meeting.
Parameter | Type | Description |
| string | The Zoom meeting ID |
write_summary_to_obsidian
Fetch a Zoom meeting summary and write it into the matching Obsidian 1:1 note. Matches the note file by the first name in the meeting topic (e.g. Amit:Howard → Amit Kumar.md). After a successful write, deletes the summary from Zoom.
Parameter | Type | Description |
| string | The numeric Zoom meeting ID (e.g. |
write_all_summaries_to_obsidian
Fetch every Zoom meeting summary and write each one to the matching Obsidian 1:1 note. Skips multi-person meetings (not 1:1s), skips meetings with no matching file, and skips duplicates already present in the note. After each successful write (including duplicates already in the vault), deletes the summary from Zoom.
Parameter | Type | Description |
| string (optional) | Start date filter (e.g. |
| string (optional) | End date filter (e.g. |
Obsidian Integration
File matching
The tool looks for a vault note to write each summary into using this priority:
Exact attendee name match — a file named
First Last.mdmatching an attendeeTopic first-name prefix — file whose name starts with the first name from the topic (e.g.
AmitfromAmit:Howard), preferring solo files over shared ones (Amit Kumar.mdoverAmit Kumar + Bob.md)Word-boundary search — broader name search as fallback
Multi-person meetings (3+ participants, or Name1:Name2:Name3 topic format) are skipped — only 1:1s are written.
Note format
Summaries are inserted in the vault's tab-indented style, newest-first:
If the date already has manual notes: Zoom content is appended below the existing notes for that day (with a blank line separator), without repeating the date header. Starts with
\tZoom AI Summary.If the date is new: A standalone
YYYY-MM-DD - Zoom AI Summarysection is inserted at the correct chronological position.
Caches
All caches are in-memory only and scoped to a single run. They exist solely to avoid fetching the same meeting twice within one execution (e.g. a meeting whose attendees were resolved in the attendee phase need not be re-fetched in the summary phase). No cache data is ever written to disk. ~/.zoom-mcp/ only holds cookies.json (session) and optionally config.json (vault path).
Dry-Run / Live Script
zoom-meetings-to-obsidian.mjs is a standalone Node.js script for previewing and applying changes.
# Dry-run: copies vault files to /tmp/obsidian-preview and applies mutations there
node zoom-meetings-to-obsidian.mjs
# Write to real vault (no deletion)
node zoom-meetings-to-obsidian.mjs --update
# Write to real vault and delete summaries from Zoom
node zoom-meetings-to-obsidian.mjs --update --delete
# Add --debug to any command for verbose diagnostics (page elements, network requests, etc.)
node zoom-meetings-to-obsidian.mjs --update --delete --debug--delete without --update is an error.
Output includes:
A table of every meeting: topic, target file, and insert/duplicate/skip status
A
Would delete from Zoomlist (dry-run) or live deletion results (--do-it)
Inspect dry-run results in /tmp/obsidian-preview before running with --do-it.
How It Works
On first use (or when cookies expire), calling
zoom_loginopens a real browser windowYou sign in to Zoom normally (SSO, password, etc. — any method works)
Session cookies are saved to
~/.zoom-mcp/cookies.jsonSubsequent calls use a headless browser with saved cookies to scrape the summaries page
Meeting summaries are written into Obsidian notes using chronological insertion
After writing, the summary is deleted from Zoom's AI Companion summary list
If cookies expire, call
zoom_loginagain
Development
npm run build # Compile TypeScript → build/
npm run dev # Watch mode (tsc --watch)
npm start # Run the MCP server (stdio transport)Version Bumping Checklist
Before committing code changes, bump the version in ALL THREE files:
package.json(main package)ObsidianPlugin/package.json(plugin package)ObsidianPlugin/manifest.json(must stay in sync with plugin package.json)
Use semantic versioning:
PATCH(x.y.Z) — bug fixes and small improvementsMINOR(x.Y.z) — new features or settingsMAJOR(X.y.z) — breaking changes
Example workflow:
# 1. Make code changes
# 2. Bump version in all three files (e.g., 1.2.10 → 1.2.11)
# 3. Rebuild
npm run build
# 4. Commit code + version bump together
git add .
git commit -m "fix/feat/docs: description here"⚠️ Never commit code changes without updating all three version numbers. If they diverge, the build output version won't match what Obsidian displays to users.
Related docs:
See
ObsidianPlugin/CLAUDE.mdfor detailed versioning requirements and consequences of version mismatch
Available Tools
5 toolsget_meeting_summaryA
Get the full AI-generated summary for a specific Zoom meeting.
Inputs: meeting_id (required).
list_meeting_summariesA
List Zoom meeting summaries. Optionally filter by date range and source (owned or shared).
Inputs: to, from, source.
write_all_summaries_to_obsidianA
Fetch every Zoom meeting summary (owned and shared) and write each one to the matching Obsidian note. Skips meetings with no matching file and skips duplicates. Shared meetings are never deleted from Zoom.
Inputs: to, from.
write_summary_to_obsidianA
Fetch a Zoom meeting summary and append it to the matching person's note in the Obsidian vault. Finds the file by matching the first name in the meeting topic (e.g. 'Amit:Howard' → Amit Kumar.md).
Inputs: meeting_id (required).
zoom_loginA
Open a browser window to log into Zoom. Call this first if you get authentication errors. Saves session cookies for reuse.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: authentication, listing summaries, retrieving a single summary, writing one summary to Obsidian, and writing all summaries. There is no overlap or ambiguity between the tools.
Tool names follow a consistent verb_noun pattern: list_meeting_summaries, get_meeting_summary, write_summary_to_obsidian, write_all_summaries_to_obsidian. 'zoom_login' is slightly different but still clear and predictable.
Five tools is well-scoped for the server's purpose of retrieving Zoom meeting summaries and exporting them to Obsidian. Each tool earns its place and the count is ideal.
The tool set covers the full workflow: login, list, get, write one, write all. Missing are any delete/update operations on summaries, but that may be outside the intended scope. Minor gap in lacking a way to fetch a summary by meeting ID directly, but workable.
Maintenance
Related MCP Connectors
Search your Obsidian vault to quickly find notes by title or keyword, summarize related content, a…
Zoom server for meetings, recordings, docs, AI search, and workflow automation.
Bring meeting decisions, tasks and user stories into your AI editor (Claude, Cursor, Copilot).
Zoom Meetings server for creating, searching, and managing meetings, recordings, and assets.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Zoom services through the Zoom API. Provides access to meeting management, user administration, and other Zoom platform features through natural language commands.-
- AlicenseAqualityCmaintenanceConnects Zotero and Obsidian for an AI-assisted academic reading workflow, enabling paper fetching, structured note creation, highlight syncing, and review management.10MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with structured access to Zoom recorded meetings, enabling search, summarization, and action item extraction.2 npmBSD 2-Clause "Simplified"
- AlicenseAqualityDmaintenanceEnables AI assistants to read, search, create, and organize notes in an Obsidian vault, with features like summarization and daily most valuable notes identification.77,721 npmMIT