Deploy to Production
varity_deployDestructive
Deploy web projects to production on Varity with automatic framework detection, building, and live hosting at a custom URL. Zero configuration required.
Instructions
Deploy the current project to production on Varity. Automatically detects the framework (Next.js, React, Vue, Express, FastAPI, etc.), builds the project, and ships it live at https://varity.app//. Zero configuration required. Dramatically cheaper than Vercel / Railway / Render. Use this when a developer wants to deploy, publish, ship, or make their app live. If the developer wants to deploy a curated AI agent (Telegram bot, chat UI, etc.) rather than their own code, use varity_deploy_agent instead. To stop a deployment and its billing, use varity_delete_deployment.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Absolute path to the project directory (e.g. '/home/user/my-app'). IMPORTANT: always pass the full absolute path to the project root, the directory that contains package.json and varity.config.json. If omitted, the MCP server's working directory is used (which is rarely the correct project root). Use the project_path returned by varity_init as the value here. | |
| app_name | No | Custom app name that controls the deployment URL: https://varity.app/{app_name}/. Must be URL-safe (lowercase letters, numbers, hyphens). If omitted, the project directory name is used. Use a different app_name than the directory to create named environments (staging, canary, etc.). | |
| repo_url | No | GitHub repository URL for the app (e.g. 'https://github.com/user/my-app'). Required for dynamic deployments. If omitted, auto-detected from .git/config. Use the repo_url returned by varity_create_repo as the value here. |