Vexa MCP Server Setup for Claude Code, Cursor and Other Apps

• Sends a bot into a meeting to record and transcribe it

  Starts a Vexa bot that joins a Google Meet, Teams or Zoom call from a meeting link or ID. If a bot is already in that meeting it says so instead of adding another.

  Try: “Send a Vexa bot to this Google Meet link.”

  Write · request_meeting_bot

• Gets the transcript of a meeting

  Returns the transcript for a meeting, with speakers labelled, whether the meeting is live or finished.

  Try: “Get the transcript of my 10am meeting.”

  Network · get_meeting_transcript

• Lists your meetings

  Returns your meetings, filtered by status or platform and paged with a limit and offset.

  Try: “List my last 10 meetings on Zoom.”

  Network · list_meetings

• Shows which bots are running

  Reports the status of your current meeting bots.

  Try: “Is a bot in my meeting right now?”

  Network · get_bot_status

• Reads a meeting link

  Works out the platform, meeting ID and passcode from a Meet, Teams or Zoom URL without calling Vexa.

  Try: “Parse this Teams link for me.”

  Read · parse_meeting_link

• Changes settings of a running bot

  Updates the configuration of a bot that is already in a meeting.

  Try: “Change the language of the bot in my meeting to Spanish.”

  Write · update_bot_config

• Removes the bot from a meeting

  Ends the bot's session in a meeting.

  Try: “Stop the Vexa bot in my current meeting.”

  Write · stop_bot

• Lists meeting recordings

  Returns your recordings.

  Try: “List my recordings from this week.”

  Network · list_recordings

• Gets one recording

  Returns the details of a single recording by its ID.

  Try: “Show me recording 123.”

  Network · get_recording

• Files a problem report with the Vexa team

  Sends a ticket with the assistant's description of a problem. It only works when the server has a ticket destination configured, and otherwise returns an error.

  Try: “Report that the transcript is missing speaker names.”

  Write · report_issue

Watch out for

• A bot in a meeting records and transcribes it

  Starting a bot puts a participant in the call that captures audio for transcripts. Tell attendees and check the rules where you work. github.com

• Hosted bot time costs money

  The README quotes $0.30 per hour of bot time on the hosted service, billed to the account that owns the API key (new accounts get $2 of free credit, about 6 hours). Watch for assistants that start bots repeatedly. github.com

• Your API key sits in the client config

  The key goes in a header in your config file. Keep the file private and revoke the key from your account page if it leaks. github.com

• The issue tool sends the assistant's text to Vexa

  When enabled on the server, report_issue posts the assistant's description and a hashed caller fingerprint, not your key, to a ticket destination. github.com

Security advisories