appdeploy-1-0-5_skill

Overview

This skill deploys web apps (frontend-only or frontend+backend) to the AppDeploy platform and returns a public URL when the build finishes. It manages API key setup, templates, file uploads, deployment status, versioning, and deletion via the platform's JSON-RPC HTTP API. Use it to publish sites, APIs, and storage-backed apps quickly with a single deploy flow.

How this skill works

Interaction happens over the AppDeploy MCP JSON-RPC endpoint using HTTP calls (curl-compatible). First call get_deploy_instructions to learn constraints, then request a base app template with get_app_template, upload your files with deploy_app, and poll get_app_status until the app is ready. Additional tools let you list apps, inspect source snapshots (src_glob, src_read, src_grep), manage versions, and permanently delete apps.

When to use it

• You need a public URL for a website, SPA, or web app with backend/API and storage.
• You want to publish changes or create a new app from a template quickly.
• You need to inspect or troubleshoot source snapshots and build logs after deployment.
• You need to roll back or apply a specific deployable version.
• You want to delete an app permanently when it’s no longer needed.

Best practices

• Always call get_deploy_instructions before generating or modifying files to satisfy platform constraints.
• For new apps, request get_app_template and submit only your custom files or diffs; templates are auto-included.
• Store the api_key in a .appdeploy file excluded from version control and reuse it for subsequent calls.
• Use get_app_status after deploy_app to check build logs, QA snapshots, and error details if deployment fails.
• When updating, send only changed files (diffs[]) or deletePaths[], and avoid removing framework entry points like package.json.

Example use cases

• Publish a marketing site built from the html-static template and get a public URL within minutes.
• Deploy a React Vite dashboard with an accompanying backend API and database integration.
• Update an existing app by sending file diffs and verify the new build via get_app_status logs.
• Inspect a deployed app’s repository with src_glob and src_read to locate and fix a runtime error.
• Apply a previous working version to roll back a bad deployment using get_app_versions and apply_app_version.