Vexa: MCP server, setup and security

What Vexa does

According to its repository: “Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Vexa is listed under Messaging and email, a category of 107 servers in the directory, where it ranks #4 by stars.

Topics declared by the repository: google-meet, meeting-assistant, meeting-minutes, meeting-notes, ms-teams, notetaker.

Installing and connecting Vexa

Distribution modes declared in the official MCP registry:

• remote server (streamable-http): you connect to it by URL, with nothing to install locally

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: Python.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Vexa. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on February 7, 2025, the Vexa-ai/vexa repository has 2,906 stars and 522 forks, with 479 open issues. It has more stars than 96% of the servers in the directory. It received changes this month. Version published in the registry: 0.12.27 (September 6, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.