A side-by-side look at the Antideploy and Shipvela MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Antideploy for cloud platforms work as a local process; choose Shipvela for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
ANTIDEPLOY_API_KEY, ANTIDEPLOY_URL.deploy, deployment_status, list_env.Rows where the two servers differ are marked.
| Spec | S Shipvela | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 56/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | ANTIDEPLOY_API_KEYANTIDEPLOY_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Antideploy | View Shipvela |
deployPackages the project directory and deploys it. Returns a `taskId`.deployment_statusProgress for one deploy: steps, the analyzed spec, warnings, hazards.list_envEnvironment variable names. Values are never returned.set_envStore or replace environment variables.api_infoThe platform API's own description of itself.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"antideploy": {
"command": "npx",
"args": [
"-y",
"antideploy-mcp"
],
"env": {
"ANTIDEPLOY_API_KEY": "YOUR_ANTIDEPLOY_API_KEY_HERE",
"ANTIDEPLOY_URL": "YOUR_ANTIDEPLOY_URL_HERE"
}
}
}
}
{
"mcpServers": {
"shipvela": {
"url": "https://shipvela.com/mcp"
}
}
}