TatNet — website deployment vs Dokploy MCP Server
A side-by-side look at the TatNet — website deployment and Dokploy MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TatNet — website deploymentCloud Platforms · Remote HTTP/SSEDeploy static and SSR websites via AI; manage Git/Docker apps, builds, logs and domains on TatNet.40FairAuth: not declaredVerdict: choose TatNet — website deployment for cloud platforms work over a hosted endpoint; choose Dokploy MCP Server 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?
TChoose TatNet — website deployment when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TatNet — website deployment | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 40/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | DOKPLOY_URLDOKPLOY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View TatNet — website deployment | View Dokploy MCP Server |
Tools & capabilities
TatNet — website deployment tools
No tool names declared yet. Check the project README from the listing page.
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 backupwebServerDokploy server backup
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.
TatNet — website deployment
{
"mcpServers": {
"tatnet-website-deployment": {
"url": "https://mcp.tatnet.cloud/mcp"
}
}
}
Dokploy MCP Server
{
"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"
}
}
}
}
Frequently asked questions
TatNet — website deployment is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Dokploy MCP Server belongs to Cloud Platforms and uses a local stdio subprocess. Pick TatNet — website deployment for cloud platforms work and Dokploy 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.
TatNet — website deployment has no declared pricing — check the project's own site. Dokploy MCP Server has no declared pricing — check the project's own site. 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 tatnet-website-deployment and dokploy-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TatNet — website deployment has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Dokploy MCP Server has 56/100 (Good) with 3 views, 0 installs and 2 GitHub stars.