RELAYTO MCP server
Connect Claude, ChatGPT, Cursor and other AI agents to your RELAYTO workspace. Sign in once, and your agent can search, publish, organize, share and measure content with your permissions.
https://mcp.relayto.com/mcpHow the RELAYTO MCP server works
RELAYTO hosts the server. Your AI client connects over Streamable HTTP, you sign in with your RELAYTO account and pick a workspace, and every tool call runs as you, within your permissions in that workspace.
- Endpoint
https://mcp.relayto.com/mcp- Transport
- Streamable HTTP
- Sign-in
- OAuth 2.1 with PKCE (S256) and dynamic client registration
- Workspace
- You pick it when you sign in. The
selectWorkspacetool lists your workspaces and switches between them. - MCP Registry
- com.relayto/mcp
- npm
- relayto-mcp, for clients that only start local (stdio) servers
Connect your AI client
Add the server URL to your client. The first connection opens RELAYTO’s sign-in page in your browser.
Claude Code
Then run
/mcpto sign in. To add the server together with RELAYTO’s agent skills, install the Claude Code plugin.Terminal claude mcp add --transport http relayto https://mcp.relayto.com/mcpClaude (web and desktop)
Settings → Connectors → Add custom connector, then enter
https://mcp.relayto.com/mcp.ChatGPT
ChatGPT connects to remote MCP servers. Add
https://mcp.relayto.com/mcpas one, and sign in with your RELAYTO account when it asks.Cursor
~/.cursor/mcp.json { "mcpServers": { "relayto": { "url": "https://mcp.relayto.com/mcp" } } }VS Code
.vscode/mcp.json { "servers": { "relayto": { "type": "http", "url": "https://mcp.relayto.com/mcp" } } }Any client that starts local (stdio) servers
The config runs
npx -y relayto-mcp: the relayto-mcp package bridges the client to the hosted server and runs the sign-in. Needs Node.js 20.18.1 or later.MCP config { "mcpServers": { "relayto": { "command": "npx", "args": ["-y", "relayto-mcp"] } } }
RELAYTO MCP tools
The server offers 31 tools, grouped here by job. Every call runs as the signed-in user, within that user’s permissions. The tools never delete contents or hubs.
Find 6
Search contents by title or by topic, search hubs, list a hub’s items.
selectWorkspaceList or switch RELAYTO workspaces read-onlygetUrlBySlugBuild a shareable RELAYTO URL read-onlygetHubItemsList items inside a RELAYTO hub read-onlysearchContentsWithAISearch RELAYTO contents (semantic) read-onlysearchContentsSearch RELAYTO contents (keyword) read-onlysearchHubsSearch RELAYTO hubs read-only
Publish 4
Create content from a PDF link, a web link, raw HTML, an image, a video or a written post; edit pages, titles, slugs and settings.
createContentCreate RELAYTO contentcreateContentByPdfUrlCreate RELAYTO content from a PDFupdateContentSettingsUpdate RELAYTO content settingsupdateContentPagesUpdate pages of a RELAYTO content
Organize 8
Create hubs; add, nest, reorder and rename items; remove items from a hub.
createNewHubCreate a new RELAYTO hubaddMultipleContentsInToHubAdd contents to a RELAYTO hubaddMultipleHubsInToHubNest hubs inside a RELAYTO hubremoveContentFromHubRemove a content from a RELAYTO hubremoveHubFromHubRemove a sub-hub from a RELAYTO hubreorderHubItemsReorder items inside a RELAYTO hubrenameMultipleContentsInHubRename contents inside a RELAYTO hubupdateHubSettingsUpdate RELAYTO hub settings
Control access 3
Public, unlisted, private, password or email gate, per content or hub; invite people to a hub by email.
updateContentPrivacyUpdate RELAYTO content privacyupdateHubPrivacyUpdate RELAYTO hub privacyaddUsersToHubInvite users to a RELAYTO hub
Files and forms 7
Host CSS, JS, fonts and images on the RELAYTO CDN; create forms and read their submissions.
listWorkspaceFilesList RELAYTO workspace files read-onlyuploadWorkspaceFileUpload a RELAYTO workspace filedeleteWorkspaceFilesDelete RELAYTO workspace filesgetWorkspaceFileUsageFind where RELAYTO workspace files are used read-onlylistFormsList RELAYTO forms read-onlycreateFormCreate a RELAYTO formgetFormSubmissionsRead RELAYTO form submissions read-only
Analytics 3
Content, hub and workspace analytics: visitors, pages read, referrers, devices, locations.
getContentAnalyticsRead RELAYTO content analytics read-onlygetHubAnalyticsRead RELAYTO hub analytics read-onlygetWorkspaceAnalyticsRead RELAYTO workspace analytics read-only
Security and sign-in
The server works only for a signed-in RELAYTO user, and only as far as that user’s own access goes.
- Your account, your permissions
- Every call runs as the signed-in RELAYTO user, in the workspace they chose, with their permissions.
- Sign-in on RELAYTO’s page
- OAuth 2.1 with PKCE. Agents never see your password.
- No deleted contents or hubs
- The tools never delete contents or hubs. Removing an item from a hub leaves the content in the workspace.
- Tokens on your machine
- In sign-in mode,
relayto-mcpcaches OAuth tokens in~/.mcp-auth. Delete that folder to sign out. - Reporting an issue
- Report security issues to support@relayto.com.
Source, packages and registry
The server’s registry entry, the npm bridge and the open-source kit with skills, agent rules and a plugin.
- relayto/relayto-mcp
GitHub: source, issues, agent skills, agent rules and the plugin
- relayto-mcp
npm: the stdio bridge for clients that only start local servers
- com.relayto/mcp
MCP Registry: this server’s entry
- Server card
The server’s name, version and endpoint as JSON
- RELAYTO API, MCP server & SDK
Guides to the RELAYTO APIs: the MCP server, the Site API, the SDK and CLI, and the OAuth content API
- RELAYTO developer docs
Read any site published on RELAYTO: its API, SDK, CLI and own MCP server