Vexa MCP Server

Content

Vexa MCP Server exposes Vexa meeting bot and transcription capabilities through MCP. It lets Claude request bots for Google Meet, Microsoft Teams, and Zoom, fetch transcripts, manage recordings, create transcript share links, control meeting chat or bot speech, configure webhooks, and work with meeting metadata.

The MCP service is implemented as a FastAPI proxy over Vexa's API gateway. The repo supports hosted Vexa API usage, Vexa Lite for a single-container self-hosted deployment, Docker Compose for multi-service deployments, and service-specific MCP docs for client setup.

Source Review

• https://github.com/Vexa-ai/vexa
• https://github.com/Vexa-ai/vexa/blob/main/README.md
• https://github.com/Vexa-ai/vexa/blob/main/docs/vexa-mcp.mdx
• https://github.com/Vexa-ai/vexa/blob/main/services/mcp/README.md
• https://github.com/Vexa-ai/vexa/blob/main/services/mcp/main.py
• https://github.com/Vexa-ai/vexa/blob/main/services/mcp/config.json
• https://github.com/Vexa-ai/vexa/blob/main/services/mcp/requirements.txt
• https://github.com/Vexa-ai/vexa/blob/main/deploy/lite/README.md
• https://github.com/Vexa-ai/vexa/blob/main/deploy/compose/README.md
• https://docs.vexa.ai
• https://docs.vexa.ai/user_api_guide
• https://docs.vexa.ai/websocket

These sources were reviewed on 2026-06-05. Prefer the live repository, README, MCP docs, MCP service source, service config, requirements, deployment guides, and Vexa docs for current tool names, deployment paths, API key handling, platform support, transcript APIs, WebSocket behavior, and service maturity.

Features

• Parse meeting links into platform, meeting ID, and passcode fields.
• Request or stop meeting bots for Google Meet, Microsoft Teams, and Zoom.
• Fetch live or post-meeting transcripts with speaker attribution.
• Create temporary transcript share links and meeting bundles.
• List, fetch, download, and delete recordings.
• Send or read meeting chat messages through an interactive bot.
• Make the bot speak with text-to-speech or stop speaking.
• Configure recording defaults, webhooks, calendar connection, and meeting metadata.
• Use a hosted Vexa endpoint or self-host Vexa Lite, Docker Compose, or Helm deployments.

Installation

For the quickest self-hosted evaluation, the repository documents Vexa Lite:

git clone https://github.com/Vexa-ai/vexa.git
cd vexa
make lite

For MCP clients, configure mcp-remote with the hosted or self-hosted MCP endpoint and an API key:

{
  "mcpServers": {
    "vexa": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "VEXA_MCP_ENDPOINT_URL",
        "--header",
        "X-API-Key: ${VEXA_API_KEY}"
      ],
      "env": {
        "VEXA_API_KEY": "${VEXA_API_KEY}"
      }
    }
  }
}

Use the hosted Vexa endpoint only when your meeting data handling policy allows it. For self-hosted deployments, use the MCP service endpoint from your own Vexa environment.

Use Cases

• Ask Claude to join a meeting as an approved notetaking bot.
• Fetch the current transcript during a live call.
• Build a post-meeting summary from transcripts, recordings, and meeting metadata.
• Send a short approved chat message from the bot.
• Trigger post-meeting transcription of a recording.
• Configure webhooks for meeting events.
• Connect calendar data for upcoming meeting workflows.
• Use self-hosting when meeting data must remain under your infrastructure.

Safety and Privacy

Meeting automation is high-trust. Obtain organizer permission and participant consent before joining, recording, transcribing, chatting, speaking, sharing screen content, or creating share links. Review Google Meet, Microsoft Teams, Zoom, and local legal requirements before use.

Treat transcripts, recordings, share links, browser sessions, chat messages, calendar events, and webhook payloads as sensitive meeting data. Hosted Vexa may send data to Vexa-operated infrastructure, while self-hosted deployments still need careful storage, retention, token, logging, and transcription-service configuration.

Duplicate Check

No Vexa-ai/vexa entry, Vexa MCP Server entry, or matching source URL was found in content/mcp.