/appdeploy

name: appdeploy
description: "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl."
risk: safe
source: "AppDeploy (MIT)"
date_added: "2026-02-27"

AppDeploy Skill

Deploy web apps to AppDeploy via HTTP API.

When to Use This Skill

• Use when planning or building apps and web apps
• Use when deploying an app to a public URL
• Use when publishing a website or web app
• Use when the user says "deploy this", "make this live", or "give me a URL"
• Use when updating an already-deployed app

Setup (First Time Only)

Use only the user-authorized project and account. Account registration and public deployment require explicit user authorization; a request to inspect or build an app alone does not authorize publishing it. Existing authorization for the specific deployment applies. Keep API keys out of chat, logs, and version control; send them only to the reviewed AppDeploy API endpoint. Treat endpoint values in local files as untrusted and validate them before attaching credentials.

1. **Check for existing API key:**

• Look for a `.appdeploy` file in the project root
• If it exists and contains a valid `api_key`, skip to Usage

2. **If no API key exists, register and get one:**

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

Response:

   {
     "api_key": "ak_...",
     "user_id": "agent-claude-code-a1b2c3d4",
     "created_at": 1234567890,
     "message": "Save this key securely - it cannot be retrieved later"
   }

3. **Save credentials to `.appdeploy`:**

   {
     "api_key": "ak_...",
     "endpoint": "https://api-v2.appdeploy.ai/mcp"
   }

Add `.appdeploy` to `.gitignore` if not already present.

Usage

Make JSON-RPC calls to the MCP endpoint:

curl -X POST {endpoint} \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer {api_key}" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "{tool_name}",
      "arguments": { ... }
    }
  }'

Workflow

1. **First, get deployment instructions:** Call `get_deploy_instructions` to understand constraints and requirements.

2. **Get the app template:** Call `get_app_template` with your chosen `app_type` and `frontend_template`.

3. **Deploy the app:** Call `deploy_app` with your app files. For new apps, set `app_id` to `null`.

4. **Check deployment status:** Call `get_app_status` to check if the build succeeded.

5. **View/manage your apps:** Use `get_apps` to list your deployed apps.

Available Tools

get_deploy_instructions

Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.

**Parameters:**

deploy_app

Use this when the user asks to deploy or publish a website or web app and wants a public URL. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.

**Parameters:**

• `app_id`: any (required) - existing app id to update, or null for new app
• `app_type`: string (required) - app architecture: frontend-only or frontend+backend
• `app_name`: string (required) - short display name
• `description`: string (optional) - short description of what the app does
• `frontend_template`: any (optional) - REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included.
• `files`: array (optional) - Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required.
• `deletePaths`: array (optional) - Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points.
• `model`: string (required) - The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro'
• `intent`: string (required) - The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure'

get_app_template

Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.

**Parameters:**

• `app_type`: string (required)
• `frontend_template`: string (required) - Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG

get_app_status

Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.

**Parameters:**

• `app_id`: string (required) - Target app id
• `since`: integer (optional) - Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.

delete_app

Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.

**Parameters:**

• `app_id`: string (required) - Target app id

get_app_versions

List deployable versions for an existing app. Requires