Fireflies just became the first meeting tool in Anthropic's official Claude MCP Directory. Otter.ai launched an enterprise MCP server too. tl;dv has one as well. The "meeting data + MCP" space is heating up fast.
But all three are closed-source, cloud-only. Your meeting data — strategy discussions, financials, personnel decisions — goes through their servers.
I've been building Vexa, an open-source meeting bot API, and we've had a native MCP server since before any of them. The difference: it's Apache 2.0, and you can run the entire stack on your own infrastructure.
Setup (takes ~2 minutes):
{ "mcpServers": { "vexa": { "url": "https://api.cloud.vexa.ai/mcp", "headers": {"X-API-Key": "your-key"} } } } Drop that in your Claude Desktop config, and you can ask:
- "What did we decide about pricing in last Tuesday's meeting?"
- "Summarize action items from all meetings this week"
- "Find every time [person] mentioned the deadline"
Or self-host the whole thing:
git clone https://github.com/Vexa-ai/vexa cd vexa docker compose up MCP server included. Your meeting data never leaves your network.
GitHub: https://github.com/Vexa-ai/vexa (1,700+ stars, Apache 2.0)
Happy to answer questions about MCP, the architecture, or how this compares to Fireflies/Otter's approach.
[link] [comments]