meetings-mcp

# meetings-mcp An MCP server over the output of my [meeting-transcription-pipeline](https://github.com/aminafara123/meeting-transcription-pipeline). It takes the finished transcripts (Whisper text, speaker labeled with pyannote) and exposes them as tools any MCP-capable AI client can call. The pipeline turns a recording into a long text file. Thats useful, but nobody rereads two hours of meeting. With this server a model can list the meetings, page through one, or search all of them for a topic and come back with the exact timestamp. ## Tools | Tool | What it does | |---|---| | `list_meetings()` | Every transcript with its id, length, turn count and speaker count | | `get_transcript(meeting, start)` | One page of 25 speaker turns, with the start value for the next page | | `search_transcripts(query)` | Case-insensitive search across all meetings, with meeting id, timestamp and turn number per hit | ## Setup ```bash pipx install meetings-mcp ``` `uvx meetings-mcp` works too if you prefer no install. Hacking on a clone instead: ```bash python3 -m venv .venv .venv/bin/pip install mcp ``` Wire it into Claude Code: ```bash claude mcp add meetings -- meetings-mcp ``` Running from a clone, point it at the venv instead: ```bash claude mcp add meetings -- /path/to/meetings-mcp/.venv/bin/python /path/to/meetings-mcp/meetings_mcp.py ``` ## Demo What it looks like from Claude Code: ``` > did we talk about the renewal in any recent meeting? ⏺ meetings · list_meetings() 2 meeting(s): - 2026-09-21-vendor-review: 00:41:09, 4 turns, 3 speaker(s) - 2026-09-24-weekly-sync: 00:18:47, 3 turns, 2 speaker(s) ⏺ meetings · search_transcripts("renewal") 3 match(es) for 'renewal': [2026-09-21-vendor-review @ 00:03:12, turn 1] Speaker 2: The renewal quote came in higher, about fifteen percent. [2026-09-21-vendor-review @ 00:07:40, turn 2] Speaker 1: Then we push back on the renewal before Friday. [2026-09-24-weekly-sync @ 00:12:30, turn 1] Speaker 2: The rene…