
Relay
io.github.yesrelayPublished by GitHub account yesrelayv1.0.0Updated Oct 24, 2026
Business phone and SMS for teams: calls, texts, transcripts, contacts and call flows.
Overview
Remote MCP server for Relay, a business phone and SMS app, letting an assistant read calls, texts and transcripts, manage contacts, send SMS and draft call…
- What you can do
- List teams and phone numbers, recent calls and texts, and read call transcripts with AI summaries and action items
- Search, create and update contacts in a team's address book, and list organization members
- Send a text from the team number
- List and read call flows, inspect the flow schema, create a flow from a template, save or discard a draft, and test a graph without writing
- When to use it
- Useful when a team runs its phone and texting through Relay and wants an assistant to summarize recent calls, look up or update contacts, send an SMS, or draft and check a call-routing flow before a person publishes it.
- Requirements
- Remote streamable HTTP endpoint at api.yesrelay.com; nothing to install server-side. A Relay account and an API key created in the app under Administration, Integrations & API, sent as an Authorization Bearer token. Sending texts needs a paid plan; Flow tools need Business or Scale.
Installation
In SourceWeft
- Open Relay in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.yesrelay%2Frelay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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
Source: README.md at commit e5986c0
Tools
0Version history
1- v1.0.0LatestSep 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts