Cursor app deployment
Deploy an app built with Cursor to production.
Connect Cursor to Adios MCP so Agent can inspect the current repository, prepare its runtime, build a production artifact, open a preview, read failures, and present a healthy release for approval.
Source to production
- 01Cursor source
- 02Adios workspace
- 03Build + preview + logs
- 04Human production approval
Production stays separated from the agent's preparation work until you approve the release.
Source
Reviewable files and config
Preview
Healthy before production
Evidence
Build output and runtime logs
Control
Human approval gate
Deployable projects
Keep the generated app. Add the production contract.
Adios works from the project source and its normal framework commands. It does not require the app to be regenerated in a proprietary format.
- Next.js and React applications
- Node.js APIs and workers
- Python, Go, Ruby, and .NET services
- Apps backed by Postgres, Redis, queues, or external APIs
Direct MCP connection
Keep deployment beside the Cursor agent.
Add Adios as a remote MCP server in the project-level .cursor/mcp.json or your global Cursor configuration. Cursor completes OAuth, then works with the same repository through scoped Adios tools.
{
"mcpServers": {
"adios": {
"url": "https://api.adios.dev/v1/mcp"
}
}
}Example agent prompt
Ask for a verified release, not only a deploy command.
Run this from Cursor Agent after the Adios MCP connection is authorized.
“Inspect this project and deploy it with Adios. Detect the framework and package manager, create or update adios.yaml, run the production build, fix any errors, start a healthy preview, and show me the source and configuration changes before requesting production approval.”
Reviewable configuration
The agent writes down how the app should run.
The exact manifest should match the repository. This example makes a conventional Node.js production build, port, and health endpoint explicit so the release can be reviewed and repeated.
Learn how adios.yaml worksname: vibe-app
region: de
build_cmd: npm ci && npm run build
start_cmd: npm start
runtime:
name: node@24
port: 3000
health_path: /api/healthSource-to-release workflow
Five checks between generated code and production.
- 01
Inspect the project source
Identify the framework, package manager, build output, start command, expected port, environment variables, and any stateful services before creating a release.
- 02
Make the runtime contract visible
Write or update adios.yaml so the build command, start command, runtime, port, health check, secrets, and managed resources can be reviewed beside the code.
- 03
Build and open a preview
Run the production build in an isolated workspace, start the application, and inspect a preview URL before treating the project as deployable.
- 04
Read logs and repair failures
Use build output, runtime logs, and the configured health path to diagnose failures. Apply the fix to source, then rebuild the same project rather than patching production by hand.
- 05
Review and approve production
Check the final source diff, configuration, preview, and health result. A person approves the production deployment after the agent has prepared a healthy release.
When the build fails
Give the agent evidence it can act on.
If Cursor finds a missing environment variable, type error, or wrong start command, it can read the relevant build output, change the source or adios.yaml, and rebuild. The repaired version—not an untracked production edit—is what moves forward.
build · failed
↓ inspect output
source + adios.yaml · updated
↓ rebuild and health check
preview · healthy
↓ human review
production · ready for approval
Framework deployment
Match the generated project to its runtime.
Deploy Next.js
Server-rendered routes, route handlers, static output, and persistent Node.js apps.
Open runtime guideDeploy React
Vite and other React frontends served as static or Node-backed applications.
Open runtime guideDeploy Node.js
APIs, background workers, and full-stack JavaScript services with explicit start commands.
Open runtime guideDeploy Postgres
Managed relational data for apps that need durable state and a private connection string.
Open runtime guideFAQ
Deploying Cursor apps with Adios.
Can Cursor deploy through Adios directly?
Yes. Connect the hosted Adios MCP server to Cursor, complete OAuth, and the agent can use scoped workspace, build, preview, log, and deployment tools. Production remains approval-gated.
Does Adios deploy only Next.js apps?
No. Adios supports explicit build and start commands for common frontend, full-stack, API, worker, and data-backed projects. The detected framework changes the runtime contract; the source-to-preview-to-production workflow stays consistent.
Can the AI agent deploy to production without approval?
No. The agent can prepare source, configuration, builds, previews, and diagnostics, but the production transition is approval-gated so a person can review the release first.
What happens when the production build fails?
The build output and runtime logs remain available to the workspace. The agent can use that evidence to update the source or configuration and run a new build before asking for production approval.
Vibe coding tools
Deploy from another AI coding workflow.
From source to healthy release
Let Cursor prepare the deploy. Keep production approval yours.
Start with the source you already have, verify it in an Adios preview, and promote only the release you reviewed.
Start free trial