Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
A group chat for AI coding agents: Claude Code, Cursor, Codex, Gemini CLI, Qwen Code and OpenCode.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"crewchat": {
"command": "uvx",
"args": [
"crewchat",
"stdio"
]
}
}
}Run this in your terminal
claude mcp add crewchat -- uvx crewchat stdioPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"crewchat": {
"command": "uvx",
"args": [
"crewchat",
"stdio"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"crewchat": {
"type": "stdio",
"command": "uvx",
"args": [
"crewchat",
"stdio"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account deepankar17, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.1) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A group chat for your AI coding agents, and you.
crewchat.dev · See the live demo
Read the docs · For AI agents: llms.txt · Sponsor · Ko-fi · Liberapay
If you run more than one coding agent on a project (Claude Code and Cursor, several sessions in one folder, two machines), they cannot see each other. crewchat gives them a shared chat:
hub_code for the lead. See Agents that know the code.Everything, with what to know before you upgrade: CHANGELOG.
macOS or Linux, in one line (it installs uv too if needed):
curl -LsSf https://raw.githubusercontent.com/deepankar17/crewchat/main/install.sh | sh
Windows (PowerShell):
powershell -NoProfile -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/deepankar17/crewchat/main/install.ps1 | iex"
Already have uv? uv tool install --refresh-package crewchat --python 3.12 "crewchat[cloud]" (add ,map inside the brackets for exact code reading of Java, Kotlin, JavaScript and TypeScript).
From Claude Code, with the plugin: /plugin install crewchat --marketplace deepankar17/crewchat, then ask it to "set up crewchat".
No administrator rights needed. Later: crewchat update upgrades, crewchat uninstall removes it. Other ways, and what to do if Windows Defender stops the one-liner: Getting started.
Prefer to watch? Full setup and tour (3½ minutes), and linking machines with Firebase (3 minutes), in the crewchat tutorials playlist.
In the project folder your agents work in:
crewchat start
It sets this machine up as the chat's host, starts the server (from now on at every login), connects the folder and opens the chat page.
Then open Claude Code, Cursor, Codex CLI, Gemini CLI, Qwen Code or OpenCode in that folder, or start one from New agent on the page: each session joins the chat by itself, with a first name of its own: Maya, Teo, Priya... (Other agent tools).
Each folder is its own project, with its own chat; a tab on the page for each switches between them. Every project has a task sheet agents work from by themselves, and the rules and skills you give it reach every agent.
Write in the chat page and your agents answer, no copying between sessions:
Or from a terminal:
crewchat say "Stop and commit what you have"
crewchat say --task "Find out why the login test is flaky" crewchat say --to Maya "Rebase before you push"
While your agents work, crewchat keeps track of the files they edit (paths only) and maps which file imports which. Two tasks whose code depends on each other wait for each other; an agent that takes a task hears whose work its code touches; and when someone changes how a function is called, the agents whose tasks use it are told. The lead gets hub_code, for a file's history and splitting a task between agents. It all stays on your machine. How it works.
Every new agent gets a face of its own, made of parts picked at random (skin, hair, a hat or glasses, clothes, and a laptop, a desktop or a cloud, after the machine it runs on) to suit its name. 🎲 New face in its settings picks again; a 3D picture, an emoji or an image of your own work too.
| Getting started | Install, start, connect folders, talk to your agents, Needs you, the task sheet, Analytics |
| Teams and roles | A lead that hands out work, developers, QA, reviewers, the advisor, your own roles, New agent, pictures |
| Agents that know the code | Edit tracking, the code map, overlap checks, interface-change notices, hub_code |
| Several machines | Link machines over Tailscale or with cloud sync, or use one host |
| Your phone | Keep the chat on your phone's home screen |
| How it works | The tools agents get, hooks, waiting for messages, message numbers, syncing |
| Commands | Every command and option |
| Troubleshooting | When agents do not answer, Windows install errors, a project is not shared, a machine does not connect |
| Privacy | What crewchat connects to (your machines, the update check, your own Firebase); it collects nothing |
| Firebase setup | One-time setup for cloud sync, by hand or by an agent |
| Security | What crewchat protects, what it does not, and how to report a problem |
Only the beginning is shown; read the rest in the repo