Deploy Web Apps with AppDeploy

This skill deploys web apps - with backend APIs, a database, and file storage - to AppDeploy via its HTTP API, triggered when a user asks to deploy or publish a site and wants a public URL, or asks to update an already-deployed app. First-time setup checks for a .appdeploy file in the project root; if none exists, it registers a new API key with a POST to https://api-v2.appdeploy.ai/mcp/api-key (with a client_name), receiving back an api_key, a user_id, and a warning that the key cannot be retrieved later, then saves the credentials to .appdeploy (adding it to .gitignore). All subsequent operations are JSON-RPC 2.0 calls to the MCP endpoint over curl, authenticated with a bearer token, using a tools/call method with a name and arguments payload. The documented workflow is strict about ordering: call get_deploy_instructions first (mandatory before generating any code, since it returns deployment constraints and hard rules, not an actual deployment), then get_app_template with a chosen app_type (frontend-only or frontend+backend) and frontend_template (html-static for simple sites, react-vite for SPAs/dashboards/games, or nextjs-static for multi-page apps) to get the base template and SDK types, then deploy_app with the app's files (for new apps, only custom files plus diffs to template files; for updates, only changed files as diffs, with app_id set to null for new apps) along with metadata like the coding-agent model used and the deployment's intent. After deploying, get_app_status reports build status (deploying/deleting in-progress, ready/failed/deleted terminal) plus a QA snapshot and live frontend/backend error logs. Additional tools round out the lifecycle: get_apps lists owned apps, delete_app permanently and irreversibly removes one (only on explicit user request), get_app_versions lists prior deployable versions (showing users the name field, never the raw version value, with timestamps converted to local time), apply_app_version redeploys a specific past version, and src_glob/src_grep/src_read let an agent explore and inspect an app's source snapshot (file discovery, regex search with context lines, and paginated file reading) without needing local file access.

Use this skill whenever a user asks to deploy, publish, or "make live" a web app and wants a public URL, or wants to update, check the status of, roll back, or delete an already-deployed app. It is not for local-only development workflows with no public-URL requirement, and file deletions via deletePaths only apply to updates (an existing app_id) - new apps and framework entry points/package.json cannot be deleted this way.

Input is app metadata (type, name, description, frontend template) and file contents or diffs, plus an app_id (or null for a new app). Output is a public deployment with a status reported via get_app_status (build state, QA snapshot, live error logs), and app/version listings for management and rollback.

Built on AppDeploy's HTTP JSON-RPC 2.0 MCP endpoint (https://api-v2.appdeploy.ai/mcp), authenticated via a bearer API key stored in a local .appdeploy file, called directly with curl.

curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \
  -H "Content-Type: application/json" \
  -d '{"client_name": "claude-code"}'

Agents and developers who need to take a web app from local files to a public URL - and manage its ongoing deployment, versioning, and error monitoring - through a single HTTP API rather than a hosting provider's own CLI or dashboard.