Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Business phone and SMS for teams: calls, texts, transcripts, contacts and call flows.
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 relay https://api.yesrelay.com/api/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": {
"relay": {
"url": "https://api.yesrelay.com/api/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": {
"relay": {
"type": "http",
"url": "https://api.yesrelay.com/api/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.
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 7, 2026
The registry name was verified with the GitHub account yesrelay, which owns the repo
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.
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 43 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.
Remote Model Context Protocol server for Relay, a business phone and SMS app for teams, built in Montreal.
It lets Claude, or any MCP client, work with your team's phone: list calls and texts, read call transcripts, search and update contacts, send an SMS from the team number, and draft call-routing flows.
| Endpoint | https://api.yesrelay.com/api/mcp |
| Transport | Streamable HTTP (spec 2025-06-18), stateless |
| Authentication | Authorization: Bearer |
| Tools | 16 |
| Plans | Every plan, free included |
| Documentation | https://yesrelay.com/en/api-docs |
This repository holds no server code: the server is hosted by Relay. Nothing to install on the server side.
rk_live_ and is shown once. Keep it in a secrets manager.Revoking the key in the app cuts MCP and REST access at the same instant.
claude mcp add --transport http relay https://api.yesrelay.com/api/mcp \
--header "Authorization: Bearer rk_live_..."
claude_desktop_config.json, through mcp-remote:
{
"mcpServers": { "relay": { "command": "npx", "args": ["mcp-remote", "https://api.yesrelay.com/api/mcp", "--header", "Authorization:${AUTH}"], "env": { "AUTH": "Bearer rk_live_..." } } } }
Point it at https://api.yesrelay.com/api/mcp with the Authorization header above.
| Tool | What it does |
|---|---|
relay_list_numbers | Lists the organization's teams and their phone numbers |
relay_list_calls | Recent calls of a team, newest first |
relay_get_transcript | Transcript of a call, with the AI summary and action items |
relay_list_messages | Recent texts of a team, newest first, filterable by contact |
relay_send_sms | Sends a text from the team number. Real, billed and irreversible |
| Tool | What it does |
|---|---|
relay_search_contacts | Searches a team's address book by first name, last name or company |
relay_create_contact | Adds a contact to the team's address book |
relay_update_contact | Replaces the fields of an existing contact |
relay_list_members | People in the organization and their identifiers |
| Tool | What it does |
|---|---|
relay_list_flows | Lists the organization's call flows |
relay_get_flow | Reads the live graph and the draft of a flow |
relay_flow_schema | Block types, expected fields and routing-engine rules |
relay_create_flow | Creates a number's flow from a template |
relay_save_flow_draft | Replaces the draft. Changes nothing callers hear |
relay_check_flow | Tests a graph without writing anything |
relay_discard_flow_draft | Throws away the draft and returns to what is live |
No tool publishes a flow. An agent can draft and check a call path; a person puts it live from the app.
A text sent through MCP goes through the same checks as a text sent from the app:
| Refusal code | When |
|---|---|
recipient_opted_out | The recipient replied STOP (or ARRET, UNSUBSCRIBE) to this team |
daily_limit_reached | The team's daily cap is reached (the customer's own limit, or the automatic one) |
workspace_budget_reached | The team's spending cap is reached |
sending_suspended | Outbound sending is paused by the circuit breaker; receiving continues |
What you can do also follows your plan: sending texts needs a paid plan, and the Flow tools need Business or Scale.
| Plan | Requests per minute per key | Keys |
|---|---|---|
| Free | 30 | 2 |
| Paid | 120 | 5 |
Each message in a JSON-RPC batch counts as one request.
The client shows a read error, or curl fails with error 56 ("chunk hex-length"). Some antivirus software that inspects HTTPS traffic corrupts MCP responses; we have seen it with Avast. The server answered correctly. Exclude api.yesrelay.com from your antivirus HTTPS scanning, then try again.
401 Invalid API key. The key is missing, revoked or expired. Create a new one in the app.
https://api.yesrelay.com/api/v1, reference at https://api.yesrelay.com/docshello@yesrelay.com