In-depth architectural comparison of the Arcane RMCP and Dokploy MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Arcane RMCP
Cloud Platforms · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Dokploy MCP Server
Cloud Platforms · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Arcane RMCP if you need specialized Cloud Platforms tools running via a local process. Choose Dokploy MCP Server if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Arcane RMCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: RARCANE_API_URL, RARCANE_API_KEY.
Primary tools included: MCP stdio and Streamable HTTP transports, Arcane API key authentication, Static bearer token and Google OAuth options for HTTP MCP.
Arcane RMCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Dokploy MCP Server belongs to Cloud Platforms using local stdio subprocess. Select Arcane RMCP when you need capabilities focused on cloud platforms and Dokploy MCP Server when you require tools for cloud platforms.
granular merge inside the server. Pass `set` (KEY=VALUE per line, upsert) and/or `unset` (array of KEY names). The read-modify-write happens server-side; the tool result is a masked confirmation listing only the changed key names. No untouched-key values ever enter the transcript.
getEnvKeys
returns KEY names only, sorted. Safe to read.
getEnvValuesUnsafe
**unsafe escape hatch** that returns the full `KEY=VALUE` blob. Use only when you genuinely need the values; the output is in the tool transcript and any retained agent logs.
saveEnvironment
full-replace, kept for explicit blob-set workflows.