Apisix MCP vs Dokploy MCP Server
A side-by-side look at the Apisix MCP 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.
Verdict: choose Apisix MCP for cloud platforms work as a local process; 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?
Choose Apisix MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
APISIX_SERVER_HOST, APISIX_SERVER_PORT, APISIX_ADMIN_API_PORT, APISIX_ADMIN_API_PREFIX, APISIX_ADMIN_KEY. - You want tools like
get_resource, delete_resource, send_request_to_gateway.
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 | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 63/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | APISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEY | DOKPLOY_URLDOKPLOY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 38 | 3 |
| Directory activity | 6 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 32 | 9 |
| Full listing | View Apisix MCP | View Dokploy MCP Server |
Tools & capabilities
Apisix MCP tools 32
get_resourceGet resource details by ID or list all resourcesdelete_resourceDelete a resource by IDsend_request_to_gatewaySend a request or multiple requests to the APISIX gatewaycreate_routeCreate a routeupdate_routeUpdate specific attributes of an existing routecreate_serviceCreate a serviceupdate_serviceUpdate specific attributes of an existing servicecreate_upstreamCreate an upstream service with load balancing settingsupdate_upstreamUpdate specific attributes of an existing upstreamcreate_or_update_consumerCreate a consumer, if the consumer already exists, it will be updatedget_credentialGet all credentials or a specific credential for a consumercreate_or_update_credentialCreate or update a credential for a consumer- +20 more on 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.
Apisix MCP
{
"mcpServers": {
"api7-apisix-mcp": {
"command": "npx",
"args": [
"-y",
"apisix-mcp"
],
"env": {
"APISIX_SERVER_HOST": "YOUR_APISIX_SERVER_HOST_HERE",
"APISIX_SERVER_PORT": "YOUR_APISIX_SERVER_PORT_HERE",
"APISIX_ADMIN_API_PORT": "YOUR_APISIX_ADMIN_API_PORT_HERE",
"APISIX_ADMIN_API_PREFIX": "YOUR_APISIX_ADMIN_API_PREFIX_HERE",
"APISIX_ADMIN_KEY": "YOUR_APISIX_ADMIN_KEY_HERE"
}
}
}
}
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
Apisix MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Dokploy MCP Server belongs to Cloud Platforms and uses a local stdio subprocess. Pick Apisix MCP 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.
Apisix MCP is listed as free. Auth: api key required. 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 api7-apisix-mcp and dokploy-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Apisix MCP has a quality signal of 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars. Dokploy MCP Server has 59/100 (Good) with 5 views, 0 installs and 3 GitHub stars.