Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Business phone and SMS for teams: calls, texts, transcripts, contacts and call flows.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http relay https://api.yesrelay.com/api/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"relay": {
"url": "https://api.yesrelay.com/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"relay": {
"type": "http",
"url": "https://api.yesrelay.com/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 yesrelay 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于43天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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