Connect Relay to Claude
Relay has an MCP server. Add it to Claude as a connector and Claude can hand work to your Relay agents, see and edit them, ship them to production, and check how their runs went, acting as you.
Before you start
- You need a Relay account that belongs to an organization. Relay is invite-only: ask whoever manages Relay at your organization to invite you.
- What Claude can do follows your role. Members can look; editors can also build and ship.
Connect
The server address is:
https://relayagents.co/api/mcp
Claude (web, desktop, mobile). Open Settings, go to Connectors, choose to add a custom connector, and paste the address. Then choose Connect.
Claude Code. Run the command below, then type /mcp and choose Relay to sign in.
claude mcp add --transport http relay https://relayagents.co/api/mcp
Either way, a Relay page opens in your browser. Sign in if you aren't already, pick the organization Claude should work in, and choose Allow. To switch organizations later, disconnect and connect again.
Things to ask
- “Show me my Relay agents.”
- “Ask the Collections agent who we should call today.”
- “Which of my agents have changes that aren't shipped yet?”
- “Rewrite the support agent's instructions to escalate billing questions, then show me the draft.”
- “The intake agent started failing this morning. What do its last runs say?”
What Claude can do
Look
Read-only. Available to every member.
show_agentsAn interactive roster of your agents: what is live, what has unshipped changes, and recent versions.show_approvalsWhat your agents are waiting on you to approve, as cards you approve or decline.show_dashboardOne of your Relay dashboards, with its tiles drawn from live data.list_agentsYour organization's agents.get_agentOne agent's name, description, and status.get_agent_draftAn agent's working draft: instructions, model, settings, and tools.list_agent_versionsAn agent's versions and whether each is a draft or published.list_agent_deploymentsWhich version is live in each environment.list_environmentsYour environments, and which are production.list_modelsThe models an agent can run on.list_toolsThe tools agents can be given.list_connectionsYour connections to outside services. Names and status only, never credentials.list_connection_toolsThe tools one connection provides.list_runsRecent runs: which agent ran, where, and how it ended.get_runOne run's status, timing, usage, and any error.whoamiThe organization this connection acts in, and your role there.
Use
Every member, for the agents they have access to. The agent acts as you.
run_agentHand an agent a task and get its reply. Follow-ups continue the same conversation.check_agent_runFetch the reply from an agent that was still working when run_agent returned.
Build
Editors only. Changes land on a draft; nothing in production changes.
create_agentCreate an agent with a first draft.edit_agentA form for one agent's name, description, model, instructions, and connections.save_agent_draftChange a draft's instructions, model, settings, or tools.update_agentRename an agent or rewrite its description.restore_agent_versionCopy an earlier version back into the draft.attach_agent_connectionGive an agent a connection's tools.detach_agent_connectionTake a connection's tools away from an agent.
Ship
Editors only. These change what is live, and Claude asks you first.
publish_agentFreeze the draft and make it live in production.promote_agent_versionMake a chosen published version live in a production environment.rollback_agentGo back to the version that was live before.set_agent_statusArchive an agent, or bring an archived one back.
In Claude on the web and desktop, five of these open as something you can click rather than text: the agent roster (show_agents), an agent at work and its reply (run_agent), your approvals (show_approvals), the agent editor (edit_agent), and dashboards (show_dashboard). Claude Code shows the same information as text.
When Claude runs an agent, the agent does real work with its own tools and connections. Anything it needs your approval for waits for you: the card in Claude shows what it wants to do, with Approve and Decline, and the same request is in your Relay Inbox. Only you can decide an approval. Claude cannot do it for you, even if asked.
How access works
- Claude acts as you, in the one organization you chose. It cannot reach another organization, and it cannot see agents that haven't been shared with you.
- Your role is checked on every request. If you are removed from the organization, the connection stops working at once.
- Claude never receives passwords, API keys, or other credentials stored in Relay. Connections are listed by name and status only.
- Agent instructions, settings, and run details that you ask about are sent to Claude so it can answer. See the Privacy Policy.
Disconnect
In Relay, open your name at the bottom of the sidebar to reach your member page. Under Connected apps, choose Disconnect. Claude loses access right away. An editor can do the same for anyone in the organization from Members.
You can also remove Relay from your connectors in Claude's settings, or run claude mcp remove relay in Claude Code.
Technical details
- Transport: Streamable HTTP, stateless. One endpoint,
POST /api/mcp. - Authorization: OAuth 2.1 authorization code flow with PKCE (S256) and refresh tokens. Clients register themselves through dynamic client registration.
- Discovery:
/.well-known/oauth-protected-resource/api/mcpand/.well-known/oauth-authorization-server. - Access tokens last one hour. Refresh tokens last 30 days and are replaced each time they are used. Relay stores only hashes of both.
- Interactive views follow the MCP Apps extension and are served as
ui://resources. They load nothing from the network.
Trouble connecting
- “No organization to connect.” Your account exists but nobody has invited it to an organization yet.
- A change is refused. You are a member, not an editor, in the organization you connected. Ask an editor, or ask to be made one.
- Claude asks you to sign in again. The connection lapsed after 30 days without use, or you were removed from the organization. Connect again.
Anything else: Support, or email trey@treyhulse.com.