# Deploy the App You Built in Cursor

> Add one MCP server to Cursor and the agent that wrote your app can deploy it, watch its logs and redeploy it, all without leaving the editor.

Published: 2026-09-20  
Canonical: https://agentcell.dev/deploy-cursor-app  
Markdown: https://agentcell.dev/deploy-cursor-app.md

**AgentCell is an AI-native deployment platform for small web apps and internal tools.** Cursor's agent can drive it through MCP, so "deploy this" becomes a prompt rather than a weekend.

## Setup

```sh
go install github.com/AgentCell-dev/agentcell-client/cmd/agentcell@latest
agentcell login
```

Then in the project's `.cursor/mcp.json` (or the global one):

```json
{
  "mcpServers": {
    "agentcell": { "command": "agentcell", "args": ["mcp"] }
  }
}
```

Cursor lists the eleven AgentCell tools. `deploy`, `logs` and `ps` are implemented today; the rest answer a typed `not_found` until they ship, which the agent can recognise and report rather than guess around.

## In the editor

Tell the agent to deploy the workspace as a named cell. `deploy` returns the URL, `logs` streams the app's output, and a failed build comes back with a `hint` the agent can act on.

## Use AgentCell when

- The app is for you or a small group: a dashboard, a tracker, an internal utility.
- You want it to cost nothing while nobody is using it.
- You want the agent in Cursor to stay responsible for running it.

## Use something else when

- It is a public product that must scale. See [AgentCell vs Vercel](/resources/vs-vercel/).
- You need preview deployments per pull request for a large team.

## Read next

- [AgentCell for AI coding agents](/docs/for-ai-agents/)
- [Deploy internal tools](/deploy-internal-tools/)

## What deploying looks like \*

Give AgentCell a directory and get back a URL. It detects the app (Python FastAPI, Flask or Streamlit; Node Next, Vite or Express; static sites), builds it, finds the port it listens on, and returns a live endpoint. Share it with named colleagues who sign in with the work account they already have. Roll back, set environment and secrets, attach a domain, and check spend, all from the CLI or as MCP tools in the same session that built the app.

\* **Conditions apply.** Not all of that has shipped. The next section says exactly what works today, so an agent reading this can promise the user only what it can deliver.

## How it works today (September 2026)

- **Deploy from a directory.** `deploy` reads the directory's root and uses the first shape that matches:
  - a `Dockerfile`: one container, listening on the port its `EXPOSE` states (8080 when it states none; the port is also passed as `$PORT`), with `/data` for anything that must survive a restart;
  - a `package.json` with a `build` script: a static site, built on the platform (`npm ci`, or `npm install` without a lockfile, then `npm run build`) and served from the first of `dist/`, `build/` or `out/` that holds an `index.html`. That covers Vite, Create React App, Vue, Svelte, Astro, and Next.js with `output: 'export'`;
  - an `index.html`: a static site, served as it is.
- **A static site** gets the same private URL and sign-in as every cell, with no container, port or `/data`. Use client 0.1.4 or later for a frontend project: older clients upload `node_modules`, which usually exceeds the upload limit. A Python or Node *server* (FastAPI, Flask, Streamlit, Express, Next.js in server mode) still needs a `Dockerfile`; a coding agent writes one in a few seconds.
- **Implemented operations:** `deploy`, `logs`, `ps`, `whoami`. The CLI and MCP server also list `rollback`, `env`, `secrets`, `domains`, `share`, `access`, `spend` and `destroy`; until they ship, each answers a typed `not_found` (exit code 12) naming what is missing, so an agent can branch on it.
- **Sharing and the identity-aware front door** are in private beta. Write to [hello@agentcell.dev](mailto:hello@agentcell.dev) if that is the part you need; deploying does not wait for it.
- **Idle container cells do not sleep yet.** Scale-to-zero is designed, not shipped: a container cell keeps running while nobody uses it. A static site runs no machine of its own, busy or idle. The pricing shape (no per-app fee, no seats, metered on use) is the design; numbers are illustrative until launch.

```sh
go install github.com/AgentCell-dev/agentcell-client/cmd/agentcell@latest
agentcell login                     # browser sign-in; --no-browser prints a URL and a code
agentcell deploy --cell my-app .    # prints the URL
agentcell logs my-app
```

Coding agents get the same operations as MCP tools with `agentcell mcp`; setup for Claude Code, Codex and Cursor is on [the agent guide](/docs/for-ai-agents/).