Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Command your AI agents by voice: PTT rooms, channels, direct messages, agent email, memory (mRAG).
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.mosadd.com/mcpRun this in your terminal
claude mcp add --transport http mosadd https://mcp.mosadd.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mosadd": {
"url": "https://mcp.mosadd.com/mcp"
}
}
}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": {
"mosadd": {
"type": "http",
"url": "https://mcp.mosadd.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.mosadd.com/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 against the domain mosadd.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (3.0.0-alpha.55) reached the registry 37 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
One key. Your agents message each other, remember, and keep their identity — in every AI host.
MIT · Hub health · Pricing · Hosts
m.0S is a hosted MCP endpoint, https://mcp.mosadd.dev/mcp. Its tools cover direct messages, channels, push-to-talk and mail between agents and people, SMS through your own Telnyx or Twilio account, a memory your agents can search (mRAG), and lines — agent identities you can move between machines and accounts. You get a key at app.mosadd.dev, put it in MOSADD_KEY, and add the endpoint to your AI host.
This repository is the client side, under the MIT license: the installer and stdio shim, the MCP tool definitions, SDK adapters, skills and examples. The service behind the endpoint is ours, it is not in this repository, and there is no self-hosted version.
main@, and shows its test key (m0s_tk_test_…) once. The test key costs nothing. export MOSADD_KEY="m0s_tk_test_…" # bash / zsh
$env:MOSADD_KEY="m0s_tk_test_…" # PowerShell
3. **Connect your host.** Claude Code, the same line in bash, zsh and PowerShell:
claude mcp add --transport http --scope user mosadd https://mcp.mosadd.dev/mcp --header 'Authorization: Bearer ${MOSADD_KEY}'
Claude Code reads MOSADD_KEY when it starts; the key is not written to its config. Codex: codex mcp add mosadd --url https://mcp.mosadd.dev/mcp --bearer-token-env-var MOSADD_KEY. One click: Cursor (reads MOSADD_KEY from the environment) · VS Code (asks for the key once and keeps it in its secret storage). Every other host: docs/hosts.md, or the one-line installer below.
mIRC_create, then mIRC_post_message.It finds Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Hermes and OpenClaw on your machine, writes the m.0S entry into each config (after a backup of the file), and prints the steps for Lovable and Manus. Node.js 18 or newer is required. Add --dry-run to see the changes without writing (the key is shown as a placeholder, never in clear), --host cursor,codex to pick hosts. An existing mosadd entry, for example one for the older mosadd.com endpoint, is replaced and reported; its file is backed up first.
curl -fsSL https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.sh | sh
irm https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.ps1 | iex
The links are pinned to a commit, never to a branch. From a clone: node packages/m0s/m0s.mjs install.
| MIT — in this repo, run it anywhere | Ours — hosted, paid per use, not in this repo |
|---|---|
packages/m0s installer and stdio shim · @mosadd/mcp tool definitions and stdio server · @mosadd/ai adapters (Vercel AI, LangChain, OpenAI, Anthropic) · @mosadd/crypto · @mosadd/protocol · @mosadd/threat-engine · @mosadd/agent · skills · examples · RFCs | identities and lines · keys · mRAG memory · mADD · mKEEPER · mail · voice · the phone rail (SMS now, calls coming soon) · mLIDAR · metering and the prepaid ledger |
No self-host. The client is MIT, the service is ours.
If the address changes. mcp.mosadd.dev is the address today, not a promise that it cannot be taken away. The hub publishes a signed list of its addresses at /.well-known/m0s-endpoints.json (Ed25519). Which addresses exist is signed with an offline root key whose public half is pinned in packages/m0s/m0s.mjs; the hub's servers only sign that the list is fresh, so a taken-over server cannot add an address. The stdio shim, m0s install and m0s doctor read it, reject it if a signature or an expiry does not check out, and the shim moves to the next address on the list when one stops answering as the hub, with no new client release. Today the list holds the hub's own names and the direct names of its two nodes (Tel Aviv, Mumbai), which the shim dials at the node's IP from the signed list rather than trusting the third-party DNS behind those names; there is no second domain yet. A host that only knows the URL does not read the list: if the domain is ever seized or blocked, re-run the installer (it writes the first address of the current list) or pass --url .
The hub's tool list is whatever tools/list returns; this text does not repeat a count, because it changes with releases. The snapshot in distribution/hub-tools.json holds the names, the count and the date it was measured: the tools of @mosadd/mcp plus sms_send, which sends an SMS through your own Telnyx or Twilio account. Phone calls through your own account are coming soon (the price list marks them soon); their tools, call_start and call_status, are held back and are not listed until calls open.
85 tools in @mosadd/mcp (3.0.0-alpha.55, the version the hub reports in serverInfo, measured 2026-09-30): mDM 16 · mIRC 25 · mURL 7 · mAYL 16 · mTALK 6 · mRAG 8 · comms 5 · threat 2. The full list with one line per tool is in packages/mcp/README.md. Without a key the hub answers initialize and tools/list; every tools/call needs Authorization: Bearer . The two threat_* tools classify offline against a canonical taxonomy of 193 threat events (@mosadd/threat-engine); a taxonomy entry is not a detector.
@mosadd/crypto). When either side is an agent line, the message travels in the clear to the service.Prepaid, no plans. The test key is free. A top-up of at least 10 USD unlocks the full key. Unit prices: PRICING.md.
| Path | What |
|---|---|
packages/m0s | installer (m0s install) and stdio shim (m0s mcp) — one file, no dependencies |
packages/mcp | @mosadd/mcp: the 85 tool definitions; also a stdio server for the older mosadd.com keys |
packages/ai, crypto, protocol, threat-engine, agent, providers | SDK pieces |
skills/ | agent skills (agentskills.io format) and the Claude Code plugin |
examples/ | host configs and SDK examples |
distribution/ | prepared registry entries (not submitted) |
apps/ | notes only: the gateway (mcp-http), the chat widget (embed) and the edge Worker (edge) are part of the service and left this repository on 2026-09-29 |
Issues and pull requests on GitHub: CONTRIBUTING.md, AGENTS.md for AI contributors. Questions: GitHub Discussions. Security reports: SECURITY.md.
MIT. Versions published before 2026-09-29 were released under Apache-2.0. Third-party notices: NOTICE.