joinly vs vexa
AI agents and meeting capture compared
joinly connects AI agents to live meetings through MCP, exposing meeting context and controls for voice and chat. vexa focuses on meeting bots and speaker-attributed transcripts through an API, with self-hosted agents for Markdown workspaces also available.
joinly: Let AI Agents Join and Participate in Meetings
Joinly connects AI agents to live video meetings through an MCP server, enabling them to listen, speak, chat, and use tools. It suits developers building meeting-aware agents who want a self-hosted setup and can manage its provider credentials and local runtime.
vexa: Capture and Transcribe Online Meetings
Vexa runs bots that join Google Meet, Microsoft Teams, and Zoom, then provides speaker-attributed transcripts through an API. Teams can use its hosted service or self-host the stack and connect transcripts to workspace agents.
| joinly | vexa | |
|---|---|---|
| Language | Python | Python |
| License | MIT | Apache-2.0 |
| Stars | 566 | 2.8k |
| Forks | 95 | 495 |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- joinly provides live meeting controls, transcripts, chat, participant details, and video snapshots for agents; vexa centers on bot capture and API-accessible transcripts.
- joinly supports speech and chat interaction during meetings, with configurable speech providers; vexa supports transcript streaming through Redis, while its documented open-core API uses polling.
- Both support Google Meet, Zoom, and Microsoft Teams. vexa also has built Jitsi support awaiting live validation.
- joinly is MIT-licensed and vexa is Apache-2.0-licensed; both are written in Python.
- joinly can run locally or through its hosted cloud service and offers Docker-based options; vexa offers hosted capture or a self-hosted stack with Docker, a process backend, or Kubernetes.
- joinly is aimed at developers building meeting-aware agents; vexa also targets teams connecting capture and transcripts to internal knowledge workflows.
Choose joinly if you…
- want an MCP-connected agent to listen, speak, chat, and use tools during live meetings.
- need live meeting context such as transcripts, participants, chat, or video snapshots.
- prefer configurable speech providers, including local Whisper and Kokoro options.
Choose vexa if you…
- need meeting bots that provide speaker-attributed transcripts through an API.
- want to self-host meeting capture and keep transcripts and recordings within your infrastructure.
- plan to connect meeting knowledge to Markdown workspaces and self-hosted agents.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.