Dokploy MCP Server vs Terraform MCP Server

A side-by-side look at the Dokploy MCP Server and Terraform MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dokploy MCP Server logoDokploy MCP ServerCloud Platforms · Local subprocess (stdio)Dokploy MCP server: manage apps, Docker Compose, databases, domains, backups, and servers.59GoodAuth: not declaredTerraform MCP Server logoTerraform MCP ServerCloud Platforms · Remote HTTP/SSEThe official Terraform MCP Server seamlessly integrates with the Terraform ecosystem, enabling provider discovery, module analysis, and direct Registry API integration for advanced Infrastructure as Code workflows.79GreatAuth: api key required

Verdict: choose Dokploy MCP Server for cloud platforms work as a local process; choose Terraform MCP Server for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dokploy MCP Server logoChoose Dokploy MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: DOKPLOY_URL, DOKPLOY_API_KEY.
  • You want tools like setEnvVars, getEnvKeys, getEnvValuesUnsafe.
Explore Dokploy MCP Server

Terraform MCP Server logoChoose Terraform MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
Explore Terraform MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDokploy MCP Server logoDokploy MCP ServerTerraform MCP Server logoTerraform MCP Server
CategoryCloud PlatformsCloud Platforms
Quality signal59/100 · Good79/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsDOKPLOY_URLDOKPLOY_API_KEYNone listed
Verified ownerCommunity listing Verified
GitHub stars31,553
Directory activity 5 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools9Not listed

Tools & capabilities

Dokploy MCP Server tools 9

  • setEnvVarsgranular 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.
  • getEnvKeysreturns 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.
  • saveEnvironmentfull-replace, kept for explicit blob-set workflows.
  • mongorequires `databaseUser` (no `databaseName`).
  • redisonly `databasePassword`.
  • libsqlrequires `appName` + `dockerImage` + `sqldNode` (`primary | replica`); accepts `sqldPrimaryUrl` + `enableNamespaces`.
  • composewhole-stack backup
  • webServerDokploy server backup

Terraform MCP Server 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.

Dokploy MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dokploy-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "dokploy-mcp-server"
      ],
      "env": {
        "DOKPLOY_URL": "YOUR_DOKPLOY_URL_HERE",
        "DOKPLOY_API_KEY": "YOUR_DOKPLOY_API_KEY_HERE"
      }
    }
  }
}

Terraform MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hashicorp-terraform-mcp-server": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

Frequently asked questions

Dokploy MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Dokploy MCP Server for cloud platforms work and Terraform MCP Server 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.

Dokploy MCP Server has no declared pricing — check the project's own site. Terraform MCP Server is listed as free. Auth: api key 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 dokploy-mcp-server and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dokploy MCP Server has a quality signal of 59/100 (Good) with 5 views, 0 installs and 3 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.