RelayCloud exposes an authenticated Model Context Protocol server for managing your RelayCloud resources through an MCP client.
Endpoint
Configure your MCP client to use:
The server advertises itself as RelayCloud MCP Server.
The endpoint also provides OAuth routes for clients that support MCP OAuth discovery and authorization.
Installation
OpenCode
Codex
Claude Code
Other
Edit ~/.config/opencode/opencode.json and add the MCP server:Authenticate with RelayCloud by running: Open your terminal and run:The next time you run codex, it automatically opens the OAuth flow to connect to your RelayCloud account.Alternatively, edit ~/.codex/config.toml and add the MCP configuration: Open your terminal and run:This launches an OAuth authentication flow to connect Claude Code to your RelayCloud account. Any MCP client that supports OAuth authentication is supported. Run the following command to add the MCP server to your client: Discover resources
list-organizations-toollist-projects-toollist-servers-toollist-server-services-toollist-server-service-ports-toollist-workspaces-toollist-workspace-domain-listeners-toollist-workspace-tls-configs-toollist-assistants-toollist-conversations-tool
Inspect resources
get-workspace-toolget-conversation-toolget-assistant-options-toolget-workspace-tls-config-tool
Create resources
create-project-toolcreate-server-toolcreate-workspace-toolgenerate-workspace-deploy-key-tool
Workspace creation accepts repository, deployment, package manager, web target, and domain configuration. Deploy keys are handled as encrypted, one-time inputs during workspace creation.
The deploy key tool never returns the private key in plain text. It only returns an encrypted version of the private key along with the public key, so the agent can add the public key to your repository. The private key is never persisted on RelayCloud. When creating a workspace, the agent passes the encrypted version of the private key, which RelayCloud uses only to set up the workspace’s git repository.
Assistants and lifecycle actions
prompt-assistant-tool sends a prompt to an OpenCode Assistant in a workspace or continues an existing conversation.restart-server-service-tool restarts a server service.restart-workspace-domain-listener-tool restarts a workspace domain listener.archive-assistant-tool archives an Assistant.archive-workspace-tool archives a workspace.archive-server-tool archives a server.
The prompt tool accepts a workspace ID or conversation ID and a prompt. It can also target an agent, model provider, model, and variant.
TLS operations
issue-workspace-tls-toolactivate-workspace-tls-config-tool
These tools support the workspace TLS provisioning flow. Read the returned TLS configuration and follow the required challenge or activation state before treating a certificate as active.
Resources
The server registers two guidance resources:
WorkspaceCreationGuideResourceWorkspaceTlsProvisioningGuideResource
Use these resources when your MCP client needs the expected sequence for workspace creation or TLS provisioning.
Do not paste access tokens, client secrets, orchestrator credentials, or OpenCode passwords into prompts or documentation. Use your MCP client’s secret storage.
