Meeting Chief Lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTTER_EMAIL | Yes | The email address for your Otter.ai account. | |
| OTTER_PASSWORD | Yes | The password for your Otter.ai account. | |
| OPENROUTER_API_KEY | Yes | API key for OpenRouter, used for semantic search embeddings. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meetingsB | Browse and retrieve meeting transcripts from Otter.ai. Operations: list (browse all), get (specific meeting), recent (last N days), stats (database info). |
| searchA | Search meeting transcripts. Supports semantic search (AI similarity), keyword search (exact match), and context search (includes surrounding transcript). Returns matching chunks with source citations. |
| statusC | System health, sync status, and management operations. Use health to check system state, sync to see last sync info, stats for database statistics, generate_embeddings to process pending jobs, run_sync to sync from Otter.ai. |
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 with no overlap: 'meetings' handles browsing and retrieving transcripts, 'search' focuses on finding content within transcripts, and 'status' manages system health and operations. The descriptions clearly differentiate these domains, eliminating any ambiguity for agent selection.
All tool names follow a consistent, simple noun-based pattern ('meetings', 'search', 'status') that is readable and predictable. There are no deviations in style or convention, making the set easy to navigate and understand.
With 3 tools, the count is slightly low but reasonable for a 'lite' server focused on meeting transcripts. It covers core operations (browse, search, status), though it might benefit from additional tools for actions like updating or deleting data, but it's well-scoped for its apparent purpose.
The tool set provides good coverage for browsing, searching, and managing meeting transcripts, with no obvious dead ends. Minor gaps exist, such as lack of explicit update or delete operations for transcripts, but agents can likely work around this given the server's focus on retrieval and search.