Vexa — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow meeting-platform coverage and endpoint authorization as the service evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Meeting bots, real-time transcription and searchable meeting knowledge across major conferencing platforms.

What we know

Vexa provides meeting bots and real-time speaker-attributed transcription for Google Meet, Microsoft Teams and Zoom, with hosted APIs and a self-hosted stack.

Maintenance / activity evidence

Observed Oct 3, 2026 (UTC)release: prepare v0.12.28 installation repair ( 1767)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can join meetings and access meeting transcript/knowledge data. Writes: Join meetings; Write derived knowledge-base artifacts.
API-key based for hosted/self-hosted API access.
Sensitive access: Meeting audio, Transcripts, Participant discussions

The platform participates in live meetings and processes highly sensitive communication data; consent, retention and workspace access need explicit controls.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

2,855 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

Which meeting providers and MCP authentication modes remain supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The platform participates in live meetings and processes highly sensitive communication data; consent, retention and workspace access need explicit controls.
Can join meetings and access meeting transcript/knowledge data.
API-key based for hosted/self-hosted API access.
Meeting audio/transcripts are processed; self-hosting keeps the stack under operator control.
Reviewed write actions: Join meetings; Write derived knowledge-base artifacts
Sensitive access: Meeting audio, Transcripts, Participant discussions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Hosted and self-hosted feature surfaces differ.
Meeting capture is privacy-sensitive and may require participant notice/consent.
Some platform support remains deployment-dependent.

Original activity observations

2026-10-03T20:45:24Z: release: prepare v0.12.28 installation repair ( 1767)

Technical identity

github.com/vexa-ai/vexa

Exact implementation source: https://github.com/vexa-ai/vexa ↗
Reviewed resource type: Gateway
Repository identity: Vexa-ai/vexa
Service endpoint: http://localhost:18056

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
vexa-ai/vexa
Recorded repository material and project history.
Includes references whose attribution is not established.
Evidence source ↗
vexa.ai/pricing
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Vexa offers hosted meetings/transcription and a separate self-hosted Docker deployment. Hosted usage needs no installation; self-hosted deployment requires an STT credential and Docker ≥26.
publisher setup or prerequisite · Publisher instructions
make all
Configure / authenticate
MCP100 setup guide
Choose hosted Vexa or self-hosted Compose stack; `make all` starts publisher's complete stack, not a one-line client MCP registration.
Check connection
Suggested check
Inspect hosted account connection or self-hosted app's health; do not spawn a real meeting bot for smoke test.
Remove / uninstall / revoke
MCP100 setup guide
For self-hosted Vexa stop the Compose stack with `docker compose down` from the deployed stack directory, without -v to keep volumes. For hosted Vexa remove the MCP connector/authorization from your client; do not delete meeting recordings accidentally.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Stop deployment / service · MCP100 composed guide
docker compose down

Official Documentation & Sources

What it does

Vexa provides meeting bots and real-time speaker-attributed transcription for Google Meet, Microsoft Teams and Zoom, with hosted APIs and a self-hosted stack.

Capability: Communication
Resource type: Gateway
Industry: Professional Services
Best fit: Meeting bots, real-time transcription and searchable meeting knowledge across major conferencing platforms.

Representative uses

Send bots into meetings
Stream speaker-attributed transcripts
Self-host meeting transcription
Build Markdown knowledge bases from meetings

Limitations

Hosted and self-hosted feature surfaces differ.
Meeting capture is privacy-sensitive and may require participant notice/consent.
Some platform support remains deployment-dependent.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API-key based for hosted/self-hosted API access.
Permissions: Can join meetings and access meeting transcript/knowledge data.
Data handling: Meeting audio/transcripts are processed; self-hosting keeps the stack under operator control.
Cost: freemium
Risk and cautions: The platform participates in live meetings and processes highly sensitive communication data; consent, retention and workspace access need explicit controls.

Access scope and cautions

Write actions: Join meetings Write derived knowledge-base artifacts
Sensitive access: Meeting audio Transcripts Participant discussions
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Send bots into meetings; Stream speaker-attributed transcripts; Self-host meeting transcription; Build Markdown knowledge bases from meetings.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: http://localhost:18056. Recorded transport: other. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Hosted API uses X-API-Key; self-hosted setup generates an API key.

Can it modify data or perform write operations?

Documented write actions include: Join meetings; Write derived knowledge-base artifacts. Recorded permission boundary: Can join meetings and access meeting transcript/knowledge data.

What data-handling boundary should I consider?

Meeting audio/transcripts are processed; self-hosting keeps the stack under operator control. Recorded sensitive-access context: Meeting audio; Transcripts; Participant discussions.

What limitations and risks should I check before use?

The platform participates in live meetings and processes highly sensitive communication data; consent, retention and workspace access need explicit controls. Hosted and self-hosted feature surfaces differ. Meeting capture is privacy-sensitive and may require participant notice/consent. Some platform support remains deployment-dependent. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Vexa AI is listed as First-party MCP in MCP100’s current evidence.