Vexa MCP MCP server

An official MCP server provided by Vexa that exposes meeting capabilities as standard tools and prompts. It allows agents to send bots to meetings, retrieve transcripts, manage recordings, and interact with meeting chats across Google Meet, Zoom, and Teams, facilitating automated meeting summaries and transcription workflows.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

API keyEndpoint checked 2026-10-05Operated by Vexa

MCP endpoint (Streamable HTTP)

https://api.cloud.vexa.ai/mcp

Vendor documentation

What you can do with it

Send a bot to a meeting to capture audio
Retrieve meeting transcripts with speaker labels
Search across meeting transcripts for keywords
Annotate meetings with metadata like CRM IDs

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http vexa-mcp https://api.cloud.vexa.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add vexa-mcp --url https://api.cloud.vexa.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vexa-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "vexa-mcp": {
      "url": "https://api.cloud.vexa.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "vexa-mcp": {
      "type": "streamableHttp",
      "url": "https://api.cloud.vexa.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vexa-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "vexa-mcp": {
      "type": "http",
      "url": "https://api.cloud.vexa.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http vexa-mcp https://api.cloud.vexa.ai/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "vexa-mcp": {
      "url": "https://api.cloud.vexa.ai/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "vexa-mcp": {
      "serverUrl": "https://api.cloud.vexa.ai/mcp"
    }
  }
}

See all 1,687

Do you run Vexa MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing