Home / Skills / vexa

Vexa-ai/vexa

Vexa-ai / vexa

MCP ServersPythonApache-2.0

Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS.

2.8kstars
496forks
626open issues
2026-10-02last pushed
Apache-2.0license

What it is, and how people use it

Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS. It sits on the MCP Servers shelf of the catalog, maintained by @Vexa-ai.

✓Drop-in for Claude Code, Codex CLI and Cursor - install and it just runs.
✓Read the SKILL.md / README first; most setups are one command from the docs.
✓Teams use it to standardise how agents behave across every repo in the org.
apiclaude-codecodexgoogle-meetmcp
vexa.ai

Why builders keep it installedMCP Servers benefits

Real tools, not role-play

An MCP server gives your agent typed access to a browser, database, chart engine or cloud account. It acts through the server instead of hallucinating what the API would have returned.

You decide what it can reach

Servers run on your machine or your cloud. Access is scoped per tool and can be cut mid-session, so credentials never live inside the model.

One server, every client

Cursor, Claude Desktop, Codex CLI and Windsurf all speak MCP. The config you write today keeps working when you switch editor or model.

Every action is auditable

Tool calls pass through the server, so you get a log of exactly what the agent read, wrote or clicked - the difference between a demo and something you'd run at work.

Contributorsloading from GitHub…

Languagesestimated from snapshot

  • Python 75.0%
  • Rust 13.0%
  • Shell 12.0%

Community pulsesnapshot ratios, normalized

starsforksissues ×3watchers