Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Operate the Meser 10 email and SMS platform from any MCP client. Read-only by default.
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.
MESER10_API_KEY, MESER10_USER_ID, MESER10_MODE, MESER10_MAX_RECIPIENTSValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"meser10": {
"command": "npx",
"args": [
"-y",
"@meser10/mcp-server"
],
"env": {
"MESER10_API_KEY": "your-value",
"MESER10_USER_ID": "your-value",
"MESER10_MODE": "your-value",
"MESER10_MAX_RECIPIENTS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add meser10 --env MESER10_API_KEY=your-value --env MESER10_USER_ID=your-value --env MESER10_MODE=your-value --env MESER10_MAX_RECIPIENTS=your-value -- npx -y @meser10/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"meser10": {
"command": "npx",
"args": [
"-y",
"@meser10/mcp-server"
],
"env": {
"MESER10_API_KEY": "your-value",
"MESER10_USER_ID": "your-value",
"MESER10_MODE": "your-value",
"MESER10_MAX_RECIPIENTS": "your-value"
}
}
}
}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": {
"meser10": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@meser10/mcp-server"
],
"env": {
"MESER10_API_KEY": "your-value",
"MESER10_USER_ID": "your-value",
"MESER10_MODE": "your-value",
"MESER10_MAX_RECIPIENTS": "your-value"
}
}
}
}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.
MESER10_USER_ID envMESER10_MODE envMESER10_MAX_RECIPIENTS envThese 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 7, 2026
The registry name was verified with the GitHub account meser10, 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.
You need to fill in: MESER10_API_KEY
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.0.2) reached the registry 2 months 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:★ 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.
Connect the Meser10 email & SMS platform to any MCP client (Claude, Cursor, or your own agent).
תיעוד בעברית, כולל התקנה מודרכת: https://www.meser10.co.il/features/mcp-server/
Listed in the official MCP Registry since 19 September 2026 as io.github.meser10/meser10-mcp (v1.0.2, MIT). Verify independently, no account needed:
https://registry.modelcontextprotocol.io/v0/servers?search=meser10
Two Israeli email/SMS marketing platforms appear in the official registry. This is the only one of the two published as open source and installable as a package; the other is a remote endpoint with no repository and no package.
Tools are generated from the live WSDL. Nobody hand-writes 61 tool definitions here, which means the server covers every API capability by construction and does not drift when the platform ships a new operation.
export MESER10_API_KEY=... # issued in the Meser10 UI
export MESER10_USER_ID=... # your account number - optional, see below npx @meser10/mcp-server
MESER10_USER_ID is optional at start-up. 17 of the 61 operations are authenticated by the key alone; the other 44 carry an explicit account number, and those fail with a clear message if it is not set. Set it unless you know you only need the first group. The account number is an identifier, not a secret - it is visible in the Meser10 UI.
Claude Desktop / Claude Code:
{
"mcpServers": { "meser10": { "command": "npx", "args": ["-y", "@meser10/mcp-server"], "env": { "MESER10_API_KEY": "...", "MESER10_USER_ID": "..." } } } }
The server starts read-only. Nothing that spends money, messages a real person, or deletes a record is reachable until you opt in.
MESER10_MODE | Adds | Tools |
|---|---|---|
read *(default)* | the Get* family | 16 |
write | contacts, groups, campaign drafts | +27 |
send | delivers to real recipients, spends credit | +13 |
destructive | permanent deletes | +5 |
Two more guards:
oLogin and iUserID are stripped from every tool schema and filled in by the server. A model cannot see, guess, or leak them. CLoginInfo does accept UserName/Password, and this server deliberately never populates them - ApiKey only.Every operation returns HTTP 200, including failures. Success lives in the Result field of CCallResult, not in the status code. This server reads Result, throws on anything that is not Success or PartialSuccess, and attaches a remedy:
LoginFailed: bad key - MESER10_API_KEY was rejected. Reissue the key in the Meser10 UI and restart.
PartialSuccess is surfaced as a warning rather than silent success, because it means some records in a batch did not land.
Legacy variants are hidden. The contract exposes five Ex/Ex2 families (15 operations for 5 capabilities). Offering all of them makes a model choose between near-identical tools and pick wrong. The richest variant is exposed; the rest are hidden behind MESER10_EXPOSE_LEGACY=true.
Names are written for callers. GetGroupsList is what the platform calls it. list_groups is what a developer reaches for. The underlying operation name is always in the description, so nothing is hidden.
Hungarian prefixes become type hints. saGroups is an array of strings, eLang is an enum, iUserID is an int. The generator uses that to produce better schemas and human titles.
`LoginFailed` on a key that worked five minutes ago. The platform blocks the *calling IP* after a few failed authentications, and the block is long - measured at over three and three quarter hours. It reports itself as Incorrect user name or password, which is indistinguishable from a wrong key, so the instinct to reissue the key and retry makes it worse: the new key is blocked too, because the block is not on the key.
If this happens: stop calling, wait, and do not put a retry loop around authentication. Never retry an auth failure automatically - retrying is what creates the block, and on a shared server it takes down every other integration sending from the same address.
`NotEnoughPermissions`. Either the key belongs to a different account than the MESER10_USER_ID you set, or that account is real but out of your key's reach. An account number the platform cannot resolve at all fails differently, as ApplicationError, so this message does mean the number exists.
A tool returns a status and no data. Fixed in 1.0.0. Upgrade.
`PartialSuccess`. Part of a batch did not land. The server surfaces it as a warning rather than silent success; check which records are missing before you retry the whole batch.
support@meser10.co.il · 03-7440020 · Sunday to Thursday, 9:00-17:00 Israel time.
Include the operation name and the Result value you got back. Never include your API key, and if one has been shared anywhere, reissue it.
npm install && npm run build
npm test # 43 unit tests + 12 end-to-end tests over real MCP stdio
The e2e suite runs a local stand-in for the platform, so it needs no credentials and sends nothing.
Verified against the production endpoint on 2026-09-12, in read mode: authentication with ApiKey only, tool listing, and four operations returning live data through the whole chain.
Also verified locally: WSDL parsing, schema generation, safety gate, envelope construction, credential injection, error mapping, recipient cap, and the MCP protocol over stdio.
Write, send and delete operations are implemented and covered by tests against a stand-in, and have deliberately never been executed against a live account by this project.