In-depth architectural comparison of the Dokploy MCP Server and Portainer MCP 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
Dokploy MCP Server
Cloud Platforms · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Portainer MCP
Cloud Platforms · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Verdict Summary: Choose Dokploy MCP Server if you need specialized Cloud Platforms tools running via a local process. Choose Portainer MCP 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 Dokploy MCP Server when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: DOKPLOY_URL, DOKPLOY_API_KEY.
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: PORTAINER_URL, PORTAINER_API_KEY, PORTAINER_TLS_VERIFY, PORTAINER_MCP_ALLOWED_HOSTS, PORTAINER_MCP_AUTH_TOKEN, PORTAINER_MCP_TLS_CERT, PORTAINER_MCP_TLS_KEY, PORTAINER_MCP_TRUST_PROXY_AUTH.
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.
mongo
requires `databaseUser` (no `databaseName`).
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Dokploy MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Portainer MCP belongs to Cloud Platforms using local stdio subprocess. Select Dokploy MCP Server when you need capabilities focused on cloud platforms and Portainer MCP when you require tools for cloud platforms.
/🏠 - A powerful MCP server that enables AI assistants to seamlessly interact with Portainer instances, providing natural language access to container management, deployment operations, and infrastructure monitoring capabilities.