OceanToken vs Relay
A side-by-side look at the OceanToken and Relay MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OceanToken for conversational ai work as a local process; choose Relay for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OceanToken when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
Choose Relay when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RELAY_API_KEY, RELAY_BASE_URL. - You want tools like
run_model, upload_file, list_workflows.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 43/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | RELAY_API_KEYRELAY_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View OceanToken | View Relay |
Tools & capabilities
OceanToken tools
No tool names declared yet. Check the project README from the listing page.
Relay tools 7
run_modelRun any model by name and wait up to 45 supload_fileHost a file and get a URL for any `*_url` input (or an image editor's `image`), or a one-time upload slot for a local file on the hosted serverlist_workflowsList the workflow templatesrun_workflowStart a workflow run, wait up to 45 scancel_workflow_runCancel a run that is still in progressget_creditsCredit balance, promos and consumption (JWT or custom-tier superkey)get_usageUsage analytics (JWT or custom-tier superkey)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
OceanToken
{
"mcpServers": {
"oceantoken": {
"command": "npx",
"args": [
"-y",
"@oceantoken/cli@latest"
]
}
}
}
Relay
{
"mcpServers": {
"relay-4": {
"command": "npx",
"args": [
"-y",
"@relaygpu/mcp"
],
"env": {
"RELAY_API_KEY": "YOUR_RELAY_API_KEY_HERE",
"RELAY_BASE_URL": "YOUR_RELAY_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
OceanToken is categorized under Conversational AI and uses a local stdio subprocess. Relay belongs to Conversational AI and uses a local stdio subprocess. Pick OceanToken for conversational ai work and Relay for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
OceanToken has no declared pricing — check the project's own site. Relay has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add oceantoken and relay-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OceanToken has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Relay has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.