meetings-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEETINGS_DATA_DIR | No | Path to the folder containing the pipeline's transcripts (one .speakers.txt per meeting, falling back to raw Whisper .txt). The default is the author's local copy. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsA | Every transcribed meeting with its id, length, turn count and number of distinct speakers. Use the id with get_transcript. |
| get_transcriptA | One page of a meeting transcript, 25 turns from turn number start. Call again with the start value it suggests to read on. |
| search_transcriptsA | Case-insensitive substring search across every transcript. Returns each matching turn with its meeting id and timestamp, text capped. |
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 3 tools
Each tool has a clearly distinct purpose: list_meetings enumerates meetings, get_transcript fetches paginated transcript content for a known meeting id, and search_transcripts performs a global substring search. There is no overlap in resource or action, so selection errors are unlikely.
All three names follow a consistent snake_case verb_noun pattern (list_meetings, get_transcript, search_transcripts). The singular/plural difference reflects the object cardinality well and does not break the convention.
Three tools is on the low end but well-scoped for a read-only transcript server: listing, reading paginated content, and searching. No functionality feels redundant or missing enough to warrant extra tools.
The read-only surface covers the core workflows: discover meetings, read a transcript, and search across all transcripts. Minor gaps exist, such as filtering meetings by date or retrieving per-speaker data, but agents can work around these using the provided tools.