Meeting Chief Lite
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., "@Meeting Chief Lite Search my meeting history for mentions of the API migration."
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.
Meeting Chief Lite
Minimal meeting transcript sync and search MCP. Downloads meetings from Otter.ai, stores them in SQLite, and provides semantic search via MCP tools.
Features
Otter.ai Sync: Download meeting transcripts automatically
Semantic Search: Find relevant transcript chunks using embeddings
Keyword Search: Fallback for exact text matching
MCP Tools: 3 focused tools for Claude/Cursor integration
Related MCP server: sync-hub
Tools
Tool | Description |
| List, get, and browse meeting transcripts |
| Semantic and keyword search across transcripts |
| System health, sync status, and management |
Quick Start
1. Configure Environment
cp .env.example .env
# Edit .env with your credentials:
# - OTTER_EMAIL
# - OTTER_PASSWORD
# - OPENROUTER_API_KEY2. Run with Docker
# Build and run
docker compose up -d
# Or run directly
docker run -it \
-e OTTER_EMAIL=your@email.com \
-e OTTER_PASSWORD=yourpassword \
-e OPENROUTER_API_KEY=sk-or-v1-xxx \
-v meeting-chief-data:/data \
ghcr.io/smcdonnell7/meeting-chief-lite3. Configure MCP Client
Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"meeting-chief-lite": {
"command": "docker",
"args": ["run", "-i", "--rm",
"-e", "OTTER_EMAIL",
"-e", "OTTER_PASSWORD",
"-e", "OPENROUTER_API_KEY",
"-v", "meeting-chief-data:/data",
"ghcr.io/smcdonnell7/meeting-chief-lite"
]
}
}
}Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"meeting-chief-lite": {
"command": "docker",
"args": ["run", "-i", "--rm",
"-e", "OTTER_EMAIL=your@email.com",
"-e", "OTTER_PASSWORD=yourpassword",
"-e", "OPENROUTER_API_KEY=sk-or-v1-xxx",
"-v", "meeting-chief-data:/data",
"ghcr.io/smcdonnell7/meeting-chief-lite"
]
}
}
}Usage Examples
# List recent meetings
meetings operation:list limit:10
# Get specific meeting
meetings operation:get id:meeting_123
# Search transcripts
search query:"API migration" mode:semantic
# Search with date filter
search query:"budget" after:2026-01-01
# Check system status
status operation:health
# Sync from Otter.ai
status operation:run_sync sync_days:30
# Generate embeddings for new meetings
status operation:generate_embeddingsDatabase
SQLite database with 7 tables:
meetings- Meeting metadata and transcriptstranscript_chunks- Parsed transcript segmentstranscript_vectors- Embeddings for semantic searchembedding_jobs- Embedding generation queuesync_runs- Sync audit logspeakers- People rosterapp_settings- Configuration
Development
# Install dependencies
npm install
# Build
npm run build
# Run locally
npm startLicense
MIT
Available Tools
3 toolsmeetingsB
Browse and retrieve meeting transcripts from Otter.ai. Operations: list (browse all), get (specific meeting), recent (last N days), stats (database info).
Inputs: operation (required), id, limit, offset, +1 more.
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.
Inputs: query (required), mode, limit, after, +3 more.
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.
Inputs: operation (required), sync_days.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Bring meeting decisions, tasks and user stories into your AI editor (Claude, Cursor, Copilot).
Otter.ai MCP server for ChatGPT, Claude and any AI agent: search transcripts, export transcript, share conversation, add highlight, upload audio and list action items in your own Otter.ai account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Otter.ai yourself; Cotlet does not store your password and you need no Otter.ai API key. About the official Otter.ai API: Yes, but narrowly (checked 16 Oct 2026). Otter.ai has an official hosted MCP server with three tools (user info, search, fetch) that only read, and a public REST API available to Enterprise workspaces that reads conversations, transcripts, action items, insights, outlines, audio, channels and the workspace, and imports a recording from a file URL. Setup and FAQ: https://cotlet.dev/integrations/otter-api-mcp-server
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.
Shared AI memory. ChatGPT, Claude, Cursor and any MCP app read and write the same memory.
Related MCP Servers
AlicenseAqualityBmaintenancePersistent memory for AI agents across Claude Code, Cowork, Codex, Cursor and Hermes Agent. Saves, searches and recalls sessions from a local SQLite store through 40+ MCP tools, with auto-save and auto-load hooks, project tagging and export/import. Also a Hermes Agent memory provider plugin in the official catalog. Free: keyword search, 50 sessions. Pro ($8/mo): semantic search and team memory.33169 PyPI12Business Source 1.1- AlicenseNot gradedqualityBmaintenanceCentralizes verbatim local AI conversation history into a SQLite database and exposes it via an MCP server, enabling tools like Claude Code and Codex to retrieve exact context from other tools.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching and reading local Cursor, Claude Code, and Codex session transcripts from any MCP client, with fuzzy, regex, and full-text search, plus optional semantic search.14MIT
- AlicenseAqualityBmaintenanceLocal memory of your coding-agent sessions. Imports Claude Code, Codex, opencode and Copilot transcripts, extracts decisions and learnings with a link back to the session turn, and lets agents search them over MCP.91MIT