# Antideploy

An MCP server that lets your coding agent ship apps to Antideploy. You approve one link, the agent handles the rest.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 3
- Author: antideploy
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/antideploy/antideploy-mcp
- Updated: 2026-10-20
- HTML: https://affpapa.org/en/nevibecode/mcp/antideploy

## What it does

Antideploy plugs the Antideploy platform into your coding agent over MCP. You say what you want built, the agent writes it and calls `login`, which returns a link and a short code. Open the link, check the code, hit Approve — that is your only manual step. From there the agent registers the application, spins up a database if the project needs one, and calls `deploy`.

The server exposes a set of tools over the platform's HTTP API: `create_application`, `deploy`, `deployment_status`, `rollback`, `logs`, `health`, `metrics`, plus environment variables, databases, storage, sign-in and email for the app. Deploys run asynchronously — `deploy`, `redeploy` and `rollback` return a `taskId`, and you poll `deployment_status` until it reads `succeeded` or `failed`. Each call already waits up to 20 seconds, so no sleep between polls.

Secrets stay out of the conversation. `login` never prints the token, and the `*_env_to_file` tools write values straight into a `.env*` file and reply with variable names only. A `.env` file is not uploaded, nor are `node_modules`, build output or private keys. A folder is bound to its application through `.antideploy.json`; a folder without one gets refused rather than matched by guesswork. Watch the limits: 4,000 files and 28 MB per project, 28 MB for a single file, one deploy per application at a time. Bigger projects go through GitHub. Deleting apps, custom domains and billing stay in the console on purpose.

## Requirements
- Needs: Node.js (commands run via npx)
- Environment variables: `ANTIDEPLOY_API_KEY`, `ANTIDEPLOY_URL` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env ANTIDEPLOY_API_KEY=<ANTIDEPLOY_API_KEY> --env ANTIDEPLOY_URL=<ANTIDEPLOY_URL> --transport stdio antideploy -- npx -y antideploy-mcp
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add antideploy --env ANTIDEPLOY_API_KEY=<ANTIDEPLOY_API_KEY> --env ANTIDEPLOY_URL=<ANTIDEPLOY_URL> -- npx -y antideploy-mcp
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "antideploy": {
            "command": "npx",
            "args": [
                "-y",
                "antideploy-mcp"
            ],
            "env": {
                "ANTIDEPLOY_API_KEY": "<ANTIDEPLOY_API_KEY>",
                "ANTIDEPLOY_URL": "<ANTIDEPLOY_URL>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "antideploy": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "antideploy-mcp"
            ],
            "env": {
                "ANTIDEPLOY_API_KEY": "<ANTIDEPLOY_API_KEY>",
                "ANTIDEPLOY_URL": "<ANTIDEPLOY_URL>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e ANTIDEPLOY_API_KEY=<ANTIDEPLOY_API_KEY> -e ANTIDEPLOY_URL=<ANTIDEPLOY_URL> antideploy npx -y antideploy-mcp
```
Replace <…> with your own values

## When to use it
- ship an agent-written app without a Dockerfile or YAML
- provision a database and write its variables into `.env`
- read deploy logs and status from inside the agent
- roll back a bad release to the previous version
- schedule a recurring task inside the app

## Example prompts
- Deploy this project on Antideploy
- Show me the logs from the last deploy and check health
- Create a database for the app and dump the variables into `.env`

## Similar
- [platform-deploy-validate](https://affpapa.org/en/nevibecode/skills/platform-deploy-validate.md) — skill · 3000 installs
- [remote-bridge](https://affpapa.org/en/nevibecode/mcp/remote-bridge.md) — MCP server · ★ 5
- [operating-kit](https://affpapa.org/en/nevibecode/plugins/operating-kit.md) — plugin · ★ 41823
- [deploy-landed](https://affpapa.org/en/nevibecode/skills/deploy-landed.md) — skill · ★ 107
- [deploy](https://affpapa.org/en/nevibecode/commands/vercel-labs-deploy.md) — command · ★ 7604
- [agents-deploy](https://affpapa.org/en/nevibecode/skills/agents-deploy.md) — skill · 2000 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md