
Relay
io.github.yesrelay由 GitHub 帳號 yesrelay 發布v1.0.0更新於 Oct 24, 2026
Business phone and SMS for teams: calls, texts, transcripts, contacts and call flows.
概覽
Relay 的遠端 MCP 伺服器,面向團隊商務電話與簡訊,讓助理查看通話、簡訊與逐字稿,管理聯絡人,發送簡訊並草擬來電流程。
- 可以做什麼
- 列出團隊與電話號碼、最近的來電和簡訊,並讀取含 AI 摘要與待辦事項的通話逐字稿
- 依名字、姓氏或公司搜尋聯絡人,新增或更新團隊通訊錄中的聯絡人,並列出組織成員
- 以團隊號碼發送簡訊
- 列出並讀取來電流程、查看流程結構說明、從範本建立流程、儲存或捨棄草稿,並在不寫入的情況下測試流程圖
- 適用情境
- 適合團隊以 Relay 處理電話與簡訊的情境:讓助理彙整近期通話、查詢或更新聯絡人、發送簡訊,或在人工上線前草擬並檢查來電轉接流程。
- 執行需求
- 遠端 streamable HTTP 端點 api.yesrelay.com,伺服器端無需安裝。需要 Relay 帳號,並在應用程式的管理、整合與 API 中建立 API 金鑰,以 Authorization Bearer 權杖方式送出。發送簡訊需付費方案,流程工具需 Business 或 Scale 方案。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Relay,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.yesrelay%2Frelay/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"relay": {
"type": "http",
"url": "https://api.yesrelay.com/api/mcp"
}
}
}README
Relay MCP server
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.
This repository holds no server code: the server is hosted by Relay. Nothing to install on the server side.
Get an API key
- Create a free account at https://app.yesrelay.com.
- In the app, open Administration, then Integrations & API, and create a key.
- The key starts with
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.
Connect a client
Claude Code
Claude Desktop
claude_desktop_config.json, through mcp-remote:
Any other client
Point it at https://api.yesrelay.com/api/mcp with the Authorization header above.
Tools
Calls and messages
Contacts and team
Flow (call routing, Business and Scale plans)
No tool publishes a flow. An agent can draft and check a call path; a person puts it live from the app.
Safeguards
A text sent through MCP goes through the same checks as a text sent from the app:
What you can do also follows your plan: sending texts needs a paid plan, and the Flow tools need Business or Scale.
Limits
Each message in a JSON-RPC batch counts as one request.
Troubleshooting
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.
Also available
- REST API:
https://api.yesrelay.com/api/v1, reference at https://api.yesrelay.com/docs - Signed webhooks (HMAC SHA-256) for call and SMS events
Support
來源:README.md,提交 e5986c0
工具
0版本歷史
1- v1.0.0最新Sep 25, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分