Vexavexa
Book a demo
MCP · Agent-native · Apache 2.0

Claude MCP
Meeting
Transcription

Point Claude at Vexa's Model Context Protocol (MCP) server to send a bot, follow a live transcript and read past meetings.

Connect ClaudeView on GitHub
2.9k stars on GitHub
vexa · api
Zoom · Teams · MeetVexa botTranscriptsYour agentMCP
  • Zoom · Teams · Meet
  • Vexa bot
  • Transcripts
  • Your agent
  • MCP
Teams
Meet
Vexa
🦀
Meeting data for your agents

Your agents read the meeting while it runs.

The transcript streams to your agents as people speak, over WebSocket or MCP.

Built for MCP agents

Vexa's MCP server wraps the public meeting API as MCP tools and prompts.

  • One command in Claude Code or one Claude Desktop connector
  • Tools to send a bot, read transcripts and list meetings
  • The same server at your own gateway's /mcp
Add Vexa to Claude Code. Full setup: https://docs.vexa.ai/vexa-mcp
claude mcp add --transport http vexa https://api.cloud.vexa.ai/mcp \
  --header "Authorization: Bearer $VEXA_API_KEY"

# Claude Desktop / claude.ai: Settings -> Connectors -> Add custom connector
#   URL: https://api.cloud.vexa.ai/mcp

# Then ask Claude:
#   "Send a bot to https://meet.google.com/abc-defg-hij
#    and tell me what they decide."
Set $API_BASE to https://api.cloud.vexa.ai (hosted) or http://localhost:18056 (self-host). Get $API_KEY from /start.

Common patterns

What you can do with Vexa over MCP

Three ways to use it, from a chat to your own agent.

Ask during the meeting

You want Claude in the meeting with you, without building anything.

What you get
  • Ask Claude to send a bot to the meeting link.
  • Then ask what was decided while the call runs.

Prep from past meetings

Before a call, you want what was said in earlier meetings with the same people.

What you get
  • Your agent lists past meetings and reads their transcripts.
  • It drafts a brief for you to check.

Inside your own agent

You are building an agent with its own tools: calendar, CRM, tickets.

What you get
  • Add Vexa's MCP server next to them.
  • The agent can send a bot from a calendar event.
  • Writing to your CRM is your agent's tool, not Vexa's.

Connect Claude to your meetings

One command in Claude Code, or one connector URL in Claude Desktop.

Quickstart

  1. Get a Vexa API keySign in at vexa.ai. Self-hosted: make all prints a key.
  2. Add the MCP serverRun the command, or add the URL as a connector.
  3. Restart your clientThe Vexa tools appear in the client's tool list.
  4. Try itAsk it to send a bot to a meeting link.
  5. Build your agentCombine Vexa's tools with your other MCP tools.
Get an API keyRead the MCP docs

MCP architecture

Vexa's MCP server is a remote server over streamable HTTP: nothing to install.

Pipeline
bot → audio capture → speech-to-text → transcript segments → REST / WebSocket

Before you start

  • Following a live meeting means polling the transcript.
  • The transcript goes to whichever model your agent runs on.
  • update_bot_config returns 404 in the 0.12 open core.

Documentation

Go deeper on MCP

Tools, prompts, authentication and self-hosting.

Full reference at docs.vexa.ai.

Related reading

Keep going on MCP

Related pages, guides and comparisons.

Claude MCP FAQ

What agent builders ask before they connect Vexa.

Which MCP clients does this work with?

Any client that supports remote MCP over streamable HTTP, such as Claude Code, Claude Desktop and claude.ai custom connectors, and agents built with the MCP SDKs.

What does the MCP server expose?

Tools that wrap the meeting API: parse a meeting link, send a bot, check its status, stop it, list meetings, read a transcript, and list or fetch recordings. It also exposes four prompts.

Can my agent follow a meeting while it runs?

Yes, by polling. The agent sends the bot, then reads the transcript every few seconds and acts on the newest segments.

Does it work with a self-hosted Vexa?

Yes. Point the client at your own gateway's /mcp instead of api.cloud.vexa.ai. The MCP server holds no credentials and touches no database: it forwards your key to the gateway.

A seat, an hour, or free

A seat for your agent. An hour for what you build. No licence fee when you run it yourself.

Pricing

Connect your agent. Your meetings, as MCP tools.

Sign in, copy an API key and add the server. Free credit, no card.

Connect your agentMCP docsGitHub

Apache 2.0 · Self-host or cloud · No credit card required