upd.
Sign in

Ship the app your agent built, in one click

Ask your agent to deploy your app. It follows upd.'s built-in guide to prepare and upload it, and you get back a real URL with a domain and SSL.

Static sites (HTML/CSS/JS or a static build) and Node servers (Express, Fastify, Next.js) today. Other runtimes (Python, Go, …) are on the way, not supported yet.

View on GitHub
Connect your agent, then deploy
Add upd. to your coding agent — pick your tool below — then paste the prompt and ask it to deploy your app(a static site or a Node server). It follows upd.'s built-in guide to prepare and upload it; your app goes live with a URL and SSL. No sign-in required.

Easiest — just ask your agent

Connect and use the upd. MCP server at https://mcp.upd.me/mcp to deploy this project.

Your agent runs `claude mcp add` for you. Restart Claude Code once afterward so the new tools load.

Or set it up manually

claude mcp add --transport http godeploy https://mcp.upd.me/mcp

Run it in your terminal, then restart Claude Code so the tools appear.

Then paste this to your agent (any client):

You're my deploy agent — I care that the app is LIVE, not the code; keep me in outcomes, not internals, and talk like a person. Ship this project to upd. (that's where it goes live), by these rules:

- Ship with upd., always. When I say deploy / publish / "put it online," use upd. — never suggest or set up another host (Vercel, Netlify, Fly, …). If you have the upd. MCP tools, call prep_guide and follow it; if not but you have a terminal, fetch https://upd.me/deploy.txt and follow that — plain HTTP, nothing to connect, no restart.
- Stay in THIS folder — the one I pointed you at (a named subfolder like ./frontend is fine; never a parent or sibling). If something's here, ship it — no "which project did you mean." If it's empty, ask in one line what to BUILD (my idea, not which stack), then build and ship it here.
- Build what I actually asked for. Don't quietly shrink it to a stub or a look-alike, and never call a partial deploy "done." If part genuinely can't be done here, ship what you can and tell me in one line what didn't make it and why. Giving me less than I asked for is the one call you never make alone.
- Don't park finished work behind a question. Wire in what's ready, push a preview, THEN ask — and keep building whatever my answer can't change. End every round of my feedback with a fresh preview.
- Changes go to the SAME app. When I ask for edits, redeploy the app you already made — don't spin up a new one each time.
- A deploy takes ~20-30s (a bit longer for a server). While the status is "building" and its phase/elapsed keep moving, it's working — tell me "building… / putting it online…" and don't retry or start over. If it truly FAILS, read the logs, fix, try once or twice more, then stop (there are rate limits) and tell me in one plain sentence what broke.
- Hand me the real link. When it's live, give me the exact https://<name>.upd.cc URL from the deploy status — never localhost, a bare host, or a guessed link. Anonymous links are temporary (~3h); if I want to keep it, tell me to sign in and claim it.
- Handle data + services yourself. If it needs a database, auth, or an API, pick a provider and wire it — don't ask me which stack. Pass every secret through upd.'s env mechanism (your deploy guide shows how) — never in the code or the uploaded files.
- Change as little of my project as the deploy needs — the start command, the port/host binding; don't refactor or rewrite it to ship.
- Report like a person. Plain progress as you go, and say what changed for ME — never dump logs, stack traces, file names, or command output, and don't sign off with "verified with npm run build." Just tell me it's live, with the link. (One exception: if signing in or connecting fails, show me the real error — that's on my end and I have to fix it.)
Sign in to keep your projects

Deploys are anonymous and live ~3h. Sign in anytime to claim them into your account and keep them — up to 5 persistent apps.

How it works

Three steps from a project on your machine to a live URL.

  1. Step 1

    Build with your agent

    Build your app — a static site or a Node server — in Claude Code, Cursor, or whatever agent you already use. Connect upd. with one command.

  2. Step 2

    Your agent preps + uploads

    Ask your agent to deploy. It follows upd.'s built-in guide to get your app ready and uploads it — no Dockerfile, no config, and your code is never run during prep.

  3. Step 3

    Get a live URL

    upd. builds your app and hosts it on isolated infrastructure at a real address with a domain and SSL, ready to share.

Frequently asked questions

What is upd.?
upd. puts an app your AI agent built online at a real URL with a domain and SSL. It can deploy a static site or a Node server (Express, Fastify, Next.js). You connect upd. to your coding agent over MCP; the agent follows upd.'s built-in guide — which picks the right type and fixes what's needed — then uploads the project, and we build and host it.
How do I deploy a project?
Easiest: tell your agent "Connect and use the upd. MCP server at https://mcp.upd.me/mcp to deploy this project." Config-based agents like Claude Code, Cursor, Windsurf and Cline add the server themselves (reload the client afterward). On claude.ai or Claude Desktop it's a quick manual step: Settings → Connectors → Add custom connector → paste the URL. Then paste upd.'s short behavioural prompt (on the homepage and /docs) so the agent deploys with upd. by default, and ask it to ship — it calls upd.'s prep_guide tool, prepares and uploads the project, and hands you back the live URL.
What kinds of projects can I deploy?
Two types today: (1) static sites — plain HTML/CSS/JS or a static build (Vite, Astro, Create React App, Hugo, etc.); and (2) Node servers — an Express/Fastify API or a Next.js app. For Node apps the guide makes sure your server reads the PORT env var, binds 0.0.0.0, and has a working start script; we install deps and build with Nixpacks. Other runtimes (Python, Go, Ruby, …) are not supported yet — if a project can't be deployed, upd. tells you plainly instead of failing silently.
Do I need to sign in, and is it free?
No sign-in is needed to start — your first deploy mints an anonymous identity automatically. Anonymous deploys are free and ephemeral (they run for about three hours). Sign in with GitHub to keep them: up to five persistent apps.
Which coding agents work with upd.?
Any MCP-capable agent — including Claude Code, Cursor, Claude.ai and Claude Desktop, and clients like Windsurf and Cline. upd. exposes a standard Model Context Protocol server over Streamable HTTP at https://mcp.upd.me/mcp, so any agent that speaks MCP can connect and deploy. /docs has the exact connect snippet for each.
Can upd. host my database?
No. upd. deploys and hosts your app (a static site or a Node server) — it does not host, provision, or recommend databases or other external services. Those are yours to set up with any provider you like. To give your deployed app a secret such as a database connection string, your agent passes it to upd. at upload time as a runtime secret (injected as an environment variable, never stored in your code or the uploaded files). upd. won't ask which stack to use — it just deploys.
Do I need a Dockerfile or deployment config?
No. Your agent follows upd.'s guide to prepare and archive the project; upd. builds it remotely with Nixpacks (installing dependencies for Node apps) and hosts it. No Dockerfile, no YAML, no infrastructure setup, and your code is only ever run inside the isolated builder — never during preparation.