Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Send and read SMS from your own Android phone and number. No per-message fees from smsportal.
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.
AuthorizationValues 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 …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http sms https://smsportal.app/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sms": {
"url": "https://smsportal.app/mcp",
"headers": {
"Authorization": "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": {
"sms": {
"type": "http",
"url": "https://smsportal.app/mcp",
"headers": {
"Authorization": "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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
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 against the domain smsportal.app (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 371 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
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 3 of 3 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: Authorization
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 (1.0.0) reached the registry 8 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.
Send and read SMS from your own Android phone through AI agents such as Claude, Cursor or any other Model Context Protocol client.
smsportal.app turns an Android phone into an SMS gateway: messages go out from your own number and SIM, and incoming SMS are available through the API. This server exposes that account to AI agents. It is not affiliated with SMSPortal (Pty) Ltd of South Africa.
Claude Code
claude mcp add --transport http smsportal https://smsportal.app/mcp \
--header "Authorization: Bearer $SMSPORTAL_API_KEY"
Claude Desktop and other clients without custom headers (via mcp-remote, Node.js 18+)
{
"mcpServers": { "smsportal": { "command": "npx", "args": ["-y", "mcp-remote", "https://smsportal.app/mcp", "--header", "Authorization:${AUTH_HEADER}"], "env": { "AUTH_HEADER": "Bearer YOUR_SMSPORTAL_API_KEY" } } } }
Step-by-step guide: smsportal.app/en/integrations/mcp.
| Tool | What it does |
|---|---|
smsportal_list_devices | Phones paired with the account and their last heartbeat and SIM state |
smsportal_get_stats | Sent, received and device totals |
smsportal_list_messages | Search sent and received SMS by text, number, phone, status and time |
smsportal_read_received_sms | Incoming SMS already synchronised by the phone |
smsportal_get_send_status | Per-recipient status of a batch returned by smsportal_send_sms |
smsportal_send_sms | Send an exact message to up to 50 E.164 numbers from your phone |
API acceptance is not proof of delivery; check the send status afterwards. Set SMSPORTAL_READ_ONLY=true to remove the sending tool.
git clone https://github.com/aleksanderem/smsportal-mcp && cd smsportal-mcp
npm ci && npm run build
Local (stdio) client entry:
{
"mcpServers": { "smsportal": { "command": "node", "args": ["/path/to/smsportal-mcp/dist/index.js"], "env": { "SMSPORTAL_API_KEY": "YOUR_SMSPORTAL_API_KEY" } } } }
| Variable | Default | Meaning |
|---|---|---|
SMSPORTAL_API_KEY | — | API key (stdio mode) |
SMSPORTAL_API_URL | https://smsportal.app/api/v1 | API base URL |
SMSPORTAL_READ_ONLY | false | true hides the sending tool |
SMSPORTAL_PUBLIC_ORIGIN | http://localhost:18080 | HTTP mode: the only browser origin allowed |
SMSPORTAL_TRUST_PROXY | false | HTTP mode: trust one reverse-proxy hop for the caller address |
HOST, PORT | 127.0.0.1, 3002 | HTTP mode listener |
HTTP mode (node dist/index.js --http, or the Dockerfile) serves Streamable HTTP at /mcp, takes the API key from Authorization: Bearer (or an x-api-key header, for hosts that cannot add the Bearer prefix), validates it before every request and rate-limits per caller network.
npm ci && npm test
Security reports: see SECURITY.md. License: MIT.