Docker MCP vs Relayer MCP
A side-by-side look at the Docker MCP and Relayer MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Relayer MCPCloud Platforms · Local subprocess (stdio)Install and manage a self-hosted XNS Relayer, S3-compatible object storage on a decentralized provider network: setup, health, configuration and backups.55GoodAuth: no auth requiredVerdict: choose Docker MCP for cloud platforms work as a local process; choose Relayer MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docker MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DOCKER_HOST, DOCKER_PORT, DOCKER_PROTOCOL, DOCKER_SOCKET_PATH, DOCKER_CERT_PATH, DOCKER_TLS_VERIFY.
Choose Relayer MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Relayer MCP | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 40/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | DOCKER_HOSTDOCKER_PORTDOCKER_PROTOCOLDOCKER_SOCKET_PATHDOCKER_CERT_PATHDOCKER_TLS_VERIFY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Docker MCP | View Relayer MCP |
Tools & capabilities
Docker MCP tools
No tool names declared yet. Check the project README from the listing page.
Relayer MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Docker MCP
{
"mcpServers": {
"docker-mcp": {
"command": "npx",
"args": [
"-y",
"@alisaitteke/docker-mcp"
],
"env": {
"DOCKER_HOST": "YOUR_DOCKER_HOST_HERE",
"DOCKER_PORT": "YOUR_DOCKER_PORT_HERE",
"DOCKER_PROTOCOL": "YOUR_DOCKER_PROTOCOL_HERE",
"DOCKER_SOCKET_PATH": "YOUR_DOCKER_SOCKET_PATH_HERE",
"DOCKER_CERT_PATH": "YOUR_DOCKER_CERT_PATH_HERE",
"DOCKER_TLS_VERIFY": "YOUR_DOCKER_TLS_VERIFY_HERE"
}
}
}
}
Relayer MCP
{
"mcpServers": {
"xns-cloud-relayer-mcp": {
"command": "npx",
"args": [
"@xns-cloud/relayer-mcp@latest"
]
}
}
}
Frequently asked questions
Docker MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Relayer MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Docker MCP for cloud platforms work and Relayer MCP for cloud platforms.
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.
Docker MCP has no declared pricing — check the project's own site. Relayer MCP has no declared pricing — check the project's own site. Auth: no auth required. 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 docker-mcp and xns-cloud-relayer-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docker MCP has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Relayer MCP has 55/100 (Good) with 0 views, 0 installs and 3 GitHub stars.