What is the key difference between Dokploy MCP Server and Infrawise?

Dokploy MCP Server belongs to the Cloud Platforms category with local stdio execution, while Infrawise belongs to the Cloud Platforms category with local stdio execution.

How do I install Dokploy MCP Server or Infrawise in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Dokploy MCP Server and Infrawise free or paid?

Dokploy MCP Server operates under a Free / Open Source model (No auth required). Infrawise operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Dokploy MCP Server lists 9 tools with 2 views and 2 GitHub stars. Infrawise lists 22 tools with 3 views and 22 GitHub stars.

Can I use both Dokploy MCP Server and Infrawise together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Dokploy MCP Server vs Infrawise

In-depth architectural comparison of the Dokploy MCP Server and Infrawise 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

Infrawise

Cloud Platforms · Local stdio

Quality: 64/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 Infrawise 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.
Primary tools included: setEnvVars, getEnvKeys, getEnvValuesUnsafe.

Explore Dokploy MCP Server Details

Choose Infrawise 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).
Primary tools included: get_infra_overview, get_graph_summary, get_table_schema.

Explore Infrawise Details

Feature & Specification Comparison

Specification	Dokploy MCP Server Cloud Platforms	Infrawise Sidd27 Cloud Platforms
Summary	Dokploy MCP server: manage apps, Docker Compose, databases, domains, backups, and servers.	Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.
Category & Scope	Cloud Platforms

Tools & Capabilities Breakdown

Dokploy MCP Server Tools (9)

setEnvVars

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 Configuration

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"
      }
    }
  }
}

Infrawise Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sidd27-infrawise": {
      "command": "npx",
      "args": [
        "-y",
        "infrawise"
      ]
    }
  }
}

Frequently Asked Questions

Dokploy MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infrawise belongs to Cloud Platforms using local stdio subprocess. Select Dokploy MCP Server when you need capabilities focused on cloud platforms and Infrawise when you require tools for cloud platforms.

More alternatives to Dokploy MCP Server More alternatives to Infrawise Cloud Platforms category hub