vibedeploy

Deploy a site (create or full-replace)

deploy_site

DestructiveIdempotent

Publish a website to a live URL. Deploy a static site or single-page app you built (with AI or by hand) to your platform subdomain (e.g. {name}.vibedeploy.be or {name}.vibedeploy.eu) with automatic SSL, and optionally a custom domain. The fastest way to get a localhost project or an AI-generated site online. DESTRUCTIVE on existing sites: replaces every file on the named site with the supplied set. Files not in this call are deleted. For a new site, creates and provisions it. For an existing site, requires confirm: "I-want-to-replace-all-files" to proceed; without confirm the call is rejected before anything is touched. Use update_site (default mode:'patch') if you want to add or change individual files without removing the rest. Use dryRun:true to preview the diff. LARGE FILES: don't split a big text file across a placeholder deploy + chunked follow-ups — a 100-250 KB HTML/CSS/JS file fits in THIS call when sent with encoding:'gzip+base64' (gzip locally, base64 the result; text compresses 3-5×). The site is published at your platform subdomain (e.g. {name}.vibedeploy.be or {name}.vibedeploy.eu). After deploy, call add_custom_domain to also serve at a user-owned hostname.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Site subdomain. Lowercase, 3-63 chars, alphanumeric + hyphens. Must not start or end with a hyphen.
`files`	Yes	Either an array of {path, content, encoding?} entries OR a path->content map. Total payload <= 500 MB.
`dryRun`	No	If true, validate input + introspect what would change but don't write or delete. Returns the same shape with `dryRun: true` and `deletedFiles` showing what would be removed. Strongly recommended before any deploy_site against an existing site.
`confirm`	No	Required when the named site already exists. Pass exactly "I-want-to-replace-all-files" to acknowledge that every existing file will be deleted and replaced with this new fileset. Omit on first deploy of a new site. If you want to add or change files without removing the others, use update_site instead — it defaults to patch mode.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Live URL of the deployed site.
`dryRun`	No	True if this was a dry-run; nothing was written or deleted.
`siteId`	Yes
`created`	Yes	True if the site was created by this call.
`warnings`	No	Surfaced issues that did not block the deploy. Common types: DOTFILE_PUBLIC (a .well-known/* file is served publicly, confirm intent), or secret-scanner findings (AWS Access Key, Stripe Key, JWT Token, etc.).
`deletedFiles`	Yes	Files that existed before this call and were removed by it. Empty for brand-new sites.
`customHeaders`	No	Result of the Netlify-style _headers sync: include a _headers file in the site root to override default response headers (e.g. Permissions-Policy). Site-wide (/*) rules only.
`filesDeployed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

removedOutput schema / properties / request_id

Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}

Changed1 schema field changedAug 19, 2026

addedOutput schema / properties / customHeaders

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "applied": {
+          "type": "number"
+        },
+        "changed": {
+          "type": "boolean"
+        },
+        "warnings": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "applied",
+        "changed",
+        "warnings"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Result of the Netlify-style _headers sync: include a _headers file in the site root to override default response headers (e.g. Permissions-Policy). Site-wide (/*) rules only."
+}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}

First observedJun 29, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations mark this as destructive, and the description goes well beyond that by specifying exactly what destruction means: 'replaces every file on the named site with the supplied set' and 'Files not in this call are deleted.' It also discloses the confirm requirement, the rejection without confirmation, and dryRun behavior to preview changes before any write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loads the critical destructive warning early. It loses a point because it repeats the platform subdomain information twice (once at the beginning and again later), and the phrase 'The fastest way to get a localhost project or an AI-generated site online' is marketing filler rather than essential operational guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists and annotations cover safety, the description covers everything an agent needs: creation vs. full-replace behavior, destructive consequences, confirmation string, dryRun preview, large-file encoding strategy, and the sibling tool to use for non-destructive updates. Nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters well. The description still adds practical value beyond the schema with guidance on large files: 'A 100-250 KB HTML/CSS/JS file fits in THIS call when sent with encoding:'gzip+base64'' and explains how to prepare the encoding. This gives agents actionable usage nuance beyond the enum descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb and resource: 'Publish a website to a live URL' and 'Deploy a static site or single-page app.' It explicitly distinguishes this from update_site by describing deploy_site as a full-replace operation, so an agent can immediately tell it apart from sibling tools like update_site or begin_deploy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use this tool, when not to, and which alternative to choose: 'Use update_site (default mode:'patch') if you want to add or change individual files without removing the rest.' It also recommends dryRun before deploying to an existing site and points to add_custom_domain as the follow-up for custom domains.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All vibedeploy tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.