VibeDeploy

Add files to a staging session

add_files

Idempotent

Add files to an open begin_deploy session; call it as often as needed, then commit_deploy publishes them together. Paths, extensions and encodings are checked on every call. A 100-250 KB text file usually fits in one call with encoding:'gzip+base64' (gzip locally, then base64); prefer that over add_file_chunk. If your shell can reach mcp.vibedeploy.be, one tar(.gz) POST to begin_deploy's uploadUrl is faster still.

Input Schema

Name	Required	Description	Default
`files`	Yes	Files to stage, same shape as in deploy_site. Re-adding a path overwrites the staged version. 500 MB per session in total.
`deployId`	Yes	Session id returned by begin_deploy.

Output Schema

Name	Required	Description
`deployId`	Yes
`warnings`	No
`filesAdded`	Yes	Files written by this call.
`totalBytes`	Yes	Total bytes staged so far across all add_files calls.
`totalFiles`	Yes	Total files now in the scratch dir.
`remainingBudget`	Yes	Bytes still available before hitting the 500 MB cap.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / files / anyOf

Previous value: -[
-  {
-    "items": {
-      "properties": {
-        "content": {
-          "type": "string"
-        },
-        "encoding": {
-          "description": "utf8 (default) for plain text. base64 for binary files (images, fonts, PDFs). gzip+base64 ships ~3–5× more raw text per tool call: gzip the bytes locally first, then base64. Server gunzips before writing. Per-file decoded size capped at 500 MB.",
-          "enum": [
-            "utf8",
-            "base64",
-            "gzip+base64"
-          ],
-          "type": "string"
-        },
-        "path": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "path",
-        "content"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Array form; needed for binary files.",
+    "items": {
+      "properties": {
+        "content": {
+          "description": "File content: text, or base64 as set by encoding.",
+          "type": "string"
+        },
+        "encoding": {
+          "description": "utf8 (default), base64 (binary files), or gzip+base64 (gzip locally, then base64; fits 3-5x more text per call).",
+          "enum": [
+            "utf8",
+            "base64",
+            "gzip+base64"
+          ],
+          "type": "string"
+        },
+        "path": {
+          "description": "Path relative to the site root, e.g. index.html or assets/app.js. Plain ASCII, no leading slash.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "path",
+        "content"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {
+      "type": "string"
+    },
+    "description": "Map form: path to UTF-8 text.",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  }
+]

changedInput schema / properties / files / description

Previous value: -"Files to append to the staging scratch dir. Same wire shape as deploy_site/update_site — array form supports binary via encoding:'base64'; map form is utf8-only. Re-adding a path overwrites the previously staged version. Cumulative cap across the whole session: 500 MB."New value: +"Files to stage, same shape as in deploy_site. Re-adding a path overwrites the staged version. 500 MB per session in total."

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 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.7/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is covered. The description adds real behavioral context: paths/extensions/encodings are validated on every call, and it gives sizing guidance (100-250 KB fits one call). It stops short of describing failure modes or error behavior, so not a full 5.

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?

Three dense sentences, all front-loaded: purpose and workflow first, validation second, encoding/sizing tip and faster alternative last. No filler and every sentence carries actionable information.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The description covers the session lifecycle, repeated-call semantics, validation behavior, and encoding/size guidance, leaving nothing an agent needs to invoke it correctly.

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 baseline is 3 and the schema already documents path/content/encoding. The description still adds practical meaning by recommending encoding:'gzip+base64' with the local gzip-then-base64 recipe and a size range where it applies, which guides parameter choice beyond the raw enum.

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?

States a specific verb and resource (add files to a staging session) and names the lifecycle siblings begin_deploy and commit_deploy, so an agent immediately understands this is the staging step between them. It also distinguishes itself from add_file_chunk by contrast.

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 when-to-use: call repeatedly against an open begin_deploy session, then commit_deploy publishes. Names an alternative (prefer gzip+base64 over add_file_chunk) and even an out-of-band faster path (tar POST to uploadUrl), giving the agent concrete routing guidance.

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.