The short answer
Any coding agent that can read a web page and make web requests can deploy to Antideploy. You have two ways to connect it. The first is one sentence that you paste into the agent. The second is the Antideploy MCP server, which you add once to an agent that supports MCP.
Start with the sentence. It covers more, because the agent follows a full procedure. Use the MCP server if you prefer tools that your agent can call by name.
Say this to your agent
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
Way 1: paste the sentence
The sentence points your agent at a page called agent.md. That page is a procedure written for agents. The agent follows it from start to finish.
-
Paste the sentence into your agent
Open your project in the agent, paste the sentence and press Enter. The agent fetches agent.md and starts following it. Claude Code, Codex, Cursor, Antigravity and Windsurf all work this way.
-
Approve one link
The agent starts a device login and shows you a link and a short code. Open the link, check that the code matches, and click Approve. If you have no account yet, the link signs you in with Google or GitHub first and takes you straight back.
-
Let the agent finish
It creates the app, creates a Postgres database if your code needs one, deploys, and tells you where the app is live and on which account.
The agent needs to reach antideploy.com. If it runs in a sandbox that blocks the network, it stops and tells you which domain to allow. You can allow it, run the agent on your own machine, or upload the folder in the Antideploy console.
Way 2: add the MCP server
MCP is a standard way for an agent to call tools. Antideploy ships an MCP server as an npm package called antideploy-mcp. It runs with npx, so there is nothing to install by hand.
-
Create the app and an API key
In the Antideploy console, create the application and then create an API key for it. The key belongs to one application, so you never pass an application id.
-
Add the server to your agent
Add the server to your agent's MCP settings. For Claude Code it is one command:
claude mcp add antideploy \ -e ANTIDEPLOY_API_KEY=ad_your_key \ -- npx -y antideploy-mcpOther agents take the same three parts in their own settings: the command
npx, the arguments-y antideploy-mcp, and the environment variableANTIDEPLOY_API_KEY. -
Start a new session and ask it to deploy
Your agent needs a new session to pick up the server. Then say "deploy this". The agent calls the
deploytool, gets back a task id, and checksdeployment_statusuntil the app is live.
The MCP server covers the essentials: deploying, checking status and setting variables. Everything beyond that is plain web requests, which every agent can already make. The server is open source under the MIT licence, on GitHub.
-
deploy. Sends your project and starts a deploy.
-
deployment_status. Follows a deploy until it succeeds or fails.
-
set_env and list_env. Sets variables and lists their names. Values are never returned.
-
api_info. Reads the full contract, every endpoint, request and limit.
Which one should I use?
Use the sentence if you want the agent to do everything: create the database, switch on storage or sign-in, set up cron jobs and read logs. You approve one link and nothing else.
Use the MCP server if your agent works best with named tools, or if you want one project key for one app that you can also use in a CI pipeline.
You can use both. An app deployed through MCP can be connected to a GitHub repository later without losing anything.