VibeKit

VibeKit Deploy

vibekit_deploy

Deploy a GitHub repo to VibeKit hosting, live at .vibekit.page (Fargate container behind nginx, SSL automatic). Use when the code already lives in a GitHub repo; for a starter template instead use vibekit_create_app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>",
      "subdomain": "<subdomain>"
    },
    "name": "vibekit_deploy"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes	GitHub repo as 'owner/repo' (e.g. 'your-username/my-app')
`subdomain`	Yes	Desired subdomain — the app goes live at <subdomain>.vibekit.page. Lowercase letters, numbers, and hyphens.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	Deploy result: deployUrl (https://<subdomain>.vibekit.page) and appId.
`error`	No	Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / subdomain / description

Previous value: -"Desired subdomain — the app goes live at <subdomain>.vibekit.bot. Lowercase letters, numbers, and hyphens."New value: +"Desired subdomain — the app goes live at <subdomain>.vibekit.page. Lowercase letters, numbers, and hyphens."

changedOutput schema / properties / data / description

Previous value: -"Deploy result: deployUrl (https://<subdomain>.vibekit.bot) and appId."New value: +"Deploy result: deployUrl (https://<subdomain>.vibekit.page) and appId."

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "Deploy result: deployUrl (https://<subdomain>.vibekit.bot) and appId."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 17, 2026

changedInput schema / properties / repo / description

Previous value: -"GitHub repo as 'owner/repo' (e.g. '609NFT/vibekit')"New value: +"GitHub repo as 'owner/repo' (e.g. 'your-username/my-app')"

First observedJul 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds useful runtime context (Fargate container behind nginx, automatic SSL) that explains what is actually provisioned. However, it never addresses the non-idempotent behavior flagged by annotations: what happens if the subdomain is taken, whether an existing deployment is replaced, how long the deploy takes, or whether it is asynchronous (the presence of vibekit_wait_for_task and vibekit_get_task siblings makes this a real question).

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?

Two sentences, front-loaded with the action and its outcome, then the routing rule. The parenthetical infrastructure note is compact and no sentence is wasted.

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

Completeness3/5

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

Return values are covered by the output schema, so the description needn't explain them. For a non-idempotent provisioning operation with two required parameters, though, it is silent on failure modes, subdomain collisions, and whether the call returns before the app is live — exactly the details an agent needs to sequence follow-up calls like vibekit_wait_for_task.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented with format and character constraints, making 3 the baseline. The description restates the subdomain-to-URL relationship and hints at the repo's role, but adds no syntax or validation detail beyond the schema.

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 ("Deploy a GitHub repo to VibeKit hosting") and pins the observable outcome ("live at <subdomain>.vibekit.page"). It also names the sibling it is not for ("for a starter template instead use vibekit_create_app"), so an agent can separate it from vibekit_create_app without opening either schema.

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

Usage Guidelines4/5

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

Gives an explicit selection condition ("Use when the code already lives in a GitHub repo") plus the alternative for the opposite case. It does not address the adjacent redeploy/rollback path (vibekit_redeploy, vibekit_rollback_deploy) for an app that already exists, which is the most likely next ambiguity an agent will hit.

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

All VibeKit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.