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.).
`request_id`	No	Server-assigned request correlation id. Quote it when contacting support.
`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

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare destructiveHint:true and readOnlyHint:false, and the description reinforces this with a prominent 'DESTRUCTIVE on existing sites' warning, explaining that files not in the call are deleted. It adds beyond annotations by specifying the confirm requirement, the file encoding trade-offs, and the subdomain publishing detail. No contradictions with annotations.

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

Conciseness5/5

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

Packed with essential information yet efficiently organized: purpose, then usage guidance, destructive warning, alternative mention, encoding tip, and custom-domain follow-up. Every sentence adds value; no filler. Despite length, it remains front-loaded with the primary action and differentiators.

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?

For a tool with four parameters, two of which are required, a destructive operation, multiple usage modes, and sibling tools, the description covers all critical aspects: purpose, behavior, alternatives, prerequisites (confirm), safety (dryRun), and support for large files and custom domains. It is arguably over-complete for a simple tool but perfectly suited to this complex deploy operation.

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

Parameters5/5

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

Schema coverage is 100% with per-property descriptions, but the tool description enriches these by explaining the destructive consequence of 'files' (deleting unspecified files), why 'confirm' is required, and that 'dryRun' is strongly recommended for existing sites. It also clarifies the encoding option's benefit (3-5x compression) beyond the schema's basic description.

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 specific verb+resource ('Publish a website to a live URL'), then clearly distinguishes deploy_site from update_site by explaining full-replacement vs. patch. It also mentions added value like automatic SSL and custom domain support, making its role unmistakable among the many sibling deployment tools.

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?

Explicit guidance is provided: 'Use update_site (default mode: patch) if you want to add or change individual files without removing the rest' and 'Use dryRun:true to preview the diff.' It also instructs to call add_custom_domain for custom domains and warns against splitting large files across multiple calls, giving concrete when-to-use and when-not-to-use context.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose, from deployment and file management to domain configuration and analytics. Even similar-sounding tools like add_files and add_file_chunk are well-differentiated by context and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_custom_domain, list_sites, delete_source_file). The naming is predictable and easy to understand.

Tool Count4/5

39 tools is higher than the typical 3-15 range, but each tool serves a necessary function for a comprehensive deployment platform. The count is justified by the broad feature set, though slightly heavy.

Completeness5/5

The tool set covers the full lifecycle of site deployment, management, backup, custom domains, form handling, analytics, and source editing. There are no obvious gaps for the intended functionality.

Deploy a site (create or full-replace)

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources