MCP tool reference · #387 of 563 by publishers
deploy
Exposed by 9 servers from 9 publishers, read from the live servers by the Serverdex check; most of them sit in Cloud & DevOps; 44.4% of them take a files parameter; the most-starred is GenHTTP Lambda (4 stars).
deploy(files: array, project_id: string, …)Parameters
share = % of the 9 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| files | array | 44.4% | 75% | Map of relative file paths to UTF-8 text content. Use when generating an app inline (e.g. from a Claude.ai web conversation). Include a framework manifest so au |
| project_id | string | 44.4% | 75% | Existing project to deploy a new version to |
| name | string | 22.2% | 0% | Human name for the tool, used when it is created (e.g. 'CRCS Finance'). |
| approvalId | string | 11.1% | 0% | Tier-2 phone approval id from a prior deploy attempt. |
| base | integer | 11.1% | 0% | The release number these files were pulled from. The deploy is refused with STALE_BASE if a newer release is live. |
| base64 | object | 11.1% | 0% | Optional binary files: relative path -> base64 of the bytes. |
| edit_token | string | 11.1% | 0% | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| expires | string | 11.1% | 0% | Optional quick-view expiry, e.g. "1h", "24h", "90s", "7d". Anonymous (unclaimed) deploys only — the link 404s after this. |
| feature | string | 11.1% | 0% | Deploy this feature to its preview address instead of a version to the lambda's. |
| force | boolean | 11.1% | 0% | If true, publish even when quality checks would block. Optional; default false. |
| hatchId | string | 11.1% | 0% | Hatch id from the original hatch response. |
| hitlTitle | string | 11.1% | 0% | Modal title for auto-opened HITL. |
Source: the input schema each server returns for deploy, aggregated over the 9 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with deploy
9 of 9 · 9 publishers · 9 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes deploy |
|---|---|---|---|---|---|---|
| 1 | GenHTTP Lambdamda2av · Cloud & DevOps | mda2av | Cloud & DevOps | 4 | yes | Deploy (publish) a saved version so it goes live at its public address - the newest by default. With feature, deploy that feature's files to its own preview address instead, against its copy of the data, leaving the lambda alone. Returns diagnostics on failure, and whatever was online stays online. |
| 2 | Boat Houseallenzhangyiteng · Cloud & DevOps | allenzhangyiteng | Cloud & DevOps | 1 | yes | Deploy a folder as a tool and make it live at https://<tool>.<workspace domain>. Send the whole folder in `files`, which MUST include a top-level Dockerfile whose process listens on $PORT (8080). Creates the tool on the first deploy; afterwards it replaces the running container. If you got these files from `pull`, pass the release number you pulled as `base` so a deploy someone else made in the me |
| 3 | Novencenovence-ai · Content & Publishing | novence-ai | Content & Publishing | 1 | yes | Publish the site. Verified accounts run quality checks; unverified accounts skip checks (checkRuns: 0) and still go live. Returns quickly — poll get_deployment_status until live or failed. Calling it again while a deploy is queued, checking, or promoting returns that same deploy; if files changed since, a follow-up deploy is queued (queuedRedeploy: true) and starts by itself once the first settles |
| 4 | Hatchviberooster · Content & Publishing | viberooster | Content & Publishing | 1 | yes | Replace the server-side code of an existing roost. Advanced — most agents should use `upload` (for static files) or `convert` (for renames) instead. Pass `hatchId`, `workerName`, and a full ES module `script` (text only, 1.5 MiB max). |
| 5 | io.sota MCPsota-deploy · Cloud & DevOps | sota-deploy | Cloud & DevOps | — | yes | Deploy an application to sota.io. The platform auto-detects your framework and builds a Docker image automatically: - Next.js: Detected via next.config.js/ts. Add output: 'standalone' to next.config for optimal builds. - Node.js: Detected via package.json with a "start" script. Works with Express, Fastify, Koa, Hapi, etc. - Python: Detected via requirements.txt or pyproject.toml. Works with Flask |
| 6 | DenkOpsdenkopsai · Cloud & DevOps | denkopsai | Cloud & DevOps | — | yes | Deploy a project to DenkOps by sending its files, and get the live URL back. Include every source file (and denkops.json if the project has one; without it a new project is created, named from `name`, package.json or pyproject.toml). Pass project_id to ship a new version of an existing project. Secrets do not belong in files: .env files are rejected (set environment variables separately). Limits: |
| 7 | aft.pageaft-page · Developer Tools | aft-page | Developer Tools | — | yes | Publish to a live URL. Pass html (one page) OR files (a built site, or a small app's source). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/; a static site needs index.html. Flask/FastAPI/Django/Express → the source files with requirements.txt or package.json; aft builds and runs it. Never upload node_modules, .venv, or .next/. First hit: |
| 8 | flinesmartline-ai · AI & Agents | smartline-ai | AI & Agents | — | yes | Build the images and hand the project to the platform. Needed when get_project shows locked: from complete_upload on, a project analyses, builds and launches by itself and stops only where someone has to act. In any other state this answers with the state, or refuses with what has to happen first. No port is taken here or anywhere else: the platform passes PORT into every container and routes to w |
| 9 | Axis Iliad - Codebase Intelligence For Agentic Commercelastmanupinc-hub · AI & Agents | lastmanupinc-hub | AI & Agents | — | yes | Generate a zero-pipeline-minutes deploy bundle: stack-aware Dockerfile, .dockerignore, dev compose, render.yaml (Render existing-image), wrangler.pages.toml + wrangler.containers.toml + worker.ts (Cloudflare), bash/PowerShell push scripts, and a qualification report. The project builds locally in VSCode, pushes images to GHCR or via wrangler, and Render/Cloudflare just pulls — no GitHub Actions mi |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.