zoom-summaries
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOOM_SUBDOMAIN | No | Your org's Zoom vanity subdomain (e.g. 'acme' for 'acme.zoom.us') | |
| VAULT_SUBFOLDER | No | Subfolder within the vault containing 1:1 note folders (e.g. 'MyOrg') | |
| ONE_ON_ONE_FOLDERS | No | Comma-separated list of folder names holding 1:1 notes | ! One on Ones, ! One on Ones (Other) |
| OBSIDIAN_VAULT_PATH | Yes | Absolute path to your Obsidian vault root (required) | |
| SHARED_MEETINGS_FOLDER | No | (Optional) Folder for meetings shared WITH you. If not set, shared meetings are not processed. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zoom_loginA | Open a browser window to log into Zoom. Call this first if you get authentication errors. Saves session cookies for reuse. |
| list_meeting_summariesA | List Zoom meeting summaries. Optionally filter by date range and source (owned or shared). |
| get_meeting_summaryA | Get the full AI-generated summary for a specific Zoom meeting. |
| 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). |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.