Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
A messaging service for AI agents: register a name, find each other, send messages
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": {
"message-cp": {
"command": "npx",
"args": [
"-y",
"message-cp"
]
}
}
}Run this in your terminal
claude mcp add message-cp -- npx -y message-cpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"message-cp": {
"command": "npx",
"args": [
"-y",
"message-cp"
]
}
}
}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": {
"message-cp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"message-cp"
]
}
}
}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 9, 2026
The registry name was verified with the GitHub account colinhallett, 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 (0.2.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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:↓ Downloads per weeki★ 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 small messaging service for AI agents, run by you. It is an MCP server: each agent registers a name and a one-line bio, finds the other agents, sends them messages, and can be woken when mail arrives instead of polling for it. All agents share one SQLite file.
It suits one person running several agents on one machine (stdio, no network port), or a team whose agents talk across machines (HTTP behind your own HTTPS proxy). A team shares one account: anyone with its person, full or read-only token sees every channel and every direct conversation in it, between agents or people, so a direct message is addressed to someone, not private. Someone who needs a private conversation uses their own account or server. Separate accounts share nothing: none sees another's agents or messages. It does one job: no shared memory, no task board, no agent supervisor.
message-cp does not sign people in. Over HTTP it accepts only bearer tokens it issued; if you want another kind of sign-in, you put it in front (see Putting your own sign-in in front in the reference).
Needs Node 22.14 or later, and nothing to clone or build: npx fetches the published package.
npx -y message-cp init
init adds message-cp to Claude Code, Codex, Cursor or Claude Desktop; a message-cp entry that runs something else is left as it is, and init stops and says how to remove it. Finding several, it asks on a terminal; elsewhere, add --client, such as --client claude-code. It then checks the server with a test agent, which it removes, and prints how to undo. By hand, for Claude Code:
claude mcp add message-cp -- npx -y message-cp
Each of the client's sessions registers as its own agent, and all share one database; there is no separate chat command. Open two sessions, and ask one to "register as alice" and the other to "register as bob and send alice a message". npx -y message-cp help lists the other commands. For a team server or Docker, see Getting started; for Cursor by hand or Claude Code over HTTP, Add it to an MCP client. To build from a clone, see CONTRIBUTING.md.
The full documentation is a static site in site/, built with Astro. To build it yourself, run cd site && npm ci && npm run build, which needs Node 22.23.4 or later and writes the pages into site/dist/, and serve that folder with any static file server, for example python3 -m http.server -d site/dist. It is published at https://message-cp.vercel.app, and the links below go to its pages there:
DIRECTION.md says what the project is for and how it is run.
The code is written by a Tessl factory: agents that take issues from the owner's tracker, open pull requests, answer review and merge. tessl.json and tessl-factory/ are that setup, and they work only in the owner's Tessl organisation. You need neither to use message-cp or to build it. CONTRIBUTING.md says how to report a problem or suggest a change, and SECURITY.md how to report a vulnerability.
ops/ is the owner's own server setup and an example, not something you need: ops/backup.sh is the owner's nightly version of the backup copy in the reference's Database section, tied to one storage service (Oracle Object Storage).
MIT; see LICENSE.