Skip to main content
Glama

vibedeploy

by be.vibedeploy
OverviewDiscussionsAdmin

Run container services (server, database, workers) for a site

deploy_app

Deploy or update the site's container services: the user's own backend server, a database (Postgres, MySQL, MongoDB, ...), Redis, background workers, from any public image. Applies the whole config: services missing from it are stopped (their volumes and data are kept). Waits until every service is ready, then returns per-service status; on failure call get_app_status with logs to debug. Each call restarts the services, which also picks up new source files. App config: { "services": { "": { "image": "postgres:16-alpine", "port": 5432, "public": false, "command": [...], "args": [...], "workingDir": "/app", "env": { "KEY": "value" }, "volumes": { "/var/lib/postgresql/data": "1Gi" }, "source": false, "sourcePath": "/app", "memory": "256Mi", "cpu": "500m" } } }. Any public image works. Services reach each other by service name (e.g. host "db", port 5432). Exactly one service may be "public": true; it receives all HTTP traffic for the site's domains on its "port" (plain HTTP, TLS is terminated for you). "source": true copies the site's source tree (write_source_files) into sourcePath (default /app, writable) on every start, so e.g. {"image":"node:22-alpine","source":true,"command":["sh","-c","npm ci && node server.js"],"port":3000,"public":true}. "${generated:NAME}" as an env value is a random secret generated once and shared by every service that references it (use it for database passwords); "$(OTHER)" embeds an earlier variable of the same service, e.g. "DATABASE_URL": "postgres://app:$(DB_PASSWORD)@db:5432/app". Secrets from outside (API keys, OAuth client secrets, tokens) never go in the config, the source or the chat: the user adds them in the VibeDeploy dashboard (the site's Settings tab, section Secrets; get_app_status returns the direct link as secrets.manageUrl). Every service gets them as env vars and restarts automatically; an explicit env entry with the same name wins. get_app_status lists the secret names that are set, never their values. Volumes persist across deploys; everything else is recreated. For Postgres set PGDATA to a subdirectory of the volume. Outbound internet works (not SMTP port 25); private networks are blocked. Limits per site: 6 services, 2048Mi memory and 2000m CPU in total (default 256Mi / 500m per service), 4 volumes, 3Gi storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
configNoThe app config object. Omit it to use vibedeploy.json from the site's source tree. App config: { "services": { "<name>": { "image": "postgres:16-alpine", "port": 5432, "public": false, "command": [...], "args": [...], "workingDir": "/app", "env": { "KEY": "value" }, "volumes": { "/var/lib/postgresql/data": "1Gi" }, "source": false, "sourcePath": "/app", "memory": "256Mi", "cpu": "500m" } } }. Any public image works. Services reach each other by service name (e.g. host "db", port 5432). Exactly one service may be "public": true; it receives all HTTP traffic for the site's domains on its "port" (plain HTTP, TLS is terminated for you). "source": true copies the site's source tree (write_source_files) into sourcePath (default /app, writable) on every start, so e.g. {"image":"node:22-alpine","source":true,"command":["sh","-c","npm ci && node server.js"],"port":3000,"public":true}. "${generated:NAME}" as an env value is a random secret generated once and shared by every service that references it (use it for database passwords); "$(OTHER)" embeds an earlier variable of the same service, e.g. "DATABASE_URL": "postgres://app:$(DB_PASSWORD)@db:5432/app". Secrets from outside (API keys, OAuth client secrets, tokens) never go in the config, the source or the chat: the user adds them in the VibeDeploy dashboard (the site's Settings tab, section Secrets; get_app_status returns the direct link as secrets.manageUrl). Every service gets them as env vars and restarts automatically; an explicit env entry with the same name wins. get_app_status lists the secret names that are set, never their values. Volumes persist across deploys; everything else is recreated. For Postgres set PGDATA to a subdirectory of the volume. Outbound internet works (not SMTP port 25); private networks are blocked. Limits per site: 6 services, 2048Mi memory and 2000m CPU in total (default 256Mi / 500m per service), 4 volumes, 3Gi storage.
siteIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / config / description
      Previous value: -"The app config object. Omit it to use vibedeploy.json from the site's source tree. App config: { \"services\": { \"<name>\": { \"image\": \"postgres:16-alpine\", \"port\": 5432, \"public\": false, \"command\": [...], \"args\": [...], \"workingDir\": \"/app\", \"env\": { \"KEY\": \"value\" }, \"volumes\": { \"/var/lib/postgresql/data\": \"1Gi\" }, \"source\": false, \"sourcePath\": \"/app\", \"memory\": \"256Mi\", \"cpu\": \"500m\" } } }. Any public image works. Services reach each other by service name (e.g. host \"db\", port 5432). Exactly one service may be \"public\": true; it receives all HTTP traffic for the site's domains on its \"port\" (plain HTTP, TLS is terminated for you). \"source\": true copies the site's source tree (write_source_files) into sourcePath (default /app, writable) on every start, so e.g. {\"image\":\"node:22-alpine\",\"source\":true,\"command\":[\"sh\",\"-c\",\"npm ci && node server.js\"],\"port\":3000,\"public\":true}. \"${generated:NAME}\" as an env value is a random secret generated once and shared by every service that references it (use it for database passwords); \"$(OTHER)\" embeds an earlier variable of the same service, e.g. \"DATABASE_URL\": \"postgres://app:$(DB_PASSWORD)@db:5432/app\". Site secrets set in the dashboard are injected as env vars too. Volumes persist across deploys; everything else is recreated. For Postgres set PGDATA to a subdirectory of the volume. Outbound internet works (not SMTP port 25); private networks are blocked. Limits per site: 6 services, 2048Mi memory and 2000m CPU in total (default 256Mi / 500m per service), 4 volumes, 3Gi storage."New value: +"The app config object. Omit it to use vibedeploy.json from the site's source tree. App config: { \"services\": { \"<name>\": { \"image\": \"postgres:16-alpine\", \"port\": 5432, \"public\": false, \"command\": [...], \"args\": [...], \"workingDir\": \"/app\", \"env\": { \"KEY\": \"value\" }, \"volumes\": { \"/var/lib/postgresql/data\": \"1Gi\" }, \"source\": false, \"sourcePath\": \"/app\", \"memory\": \"256Mi\", \"cpu\": \"500m\" } } }. Any public image works. Services reach each other by service name (e.g. host \"db\", port 5432). Exactly one service may be \"public\": true; it receives all HTTP traffic for the site's domains on its \"port\" (plain HTTP, TLS is terminated for you). \"source\": true copies the site's source tree (write_source_files) into sourcePath (default /app, writable) on every start, so e.g. {\"image\":\"node:22-alpine\",\"source\":true,\"command\":[\"sh\",\"-c\",\"npm ci && node server.js\"],\"port\":3000,\"public\":true}. \"${generated:NAME}\" as an env value is a random secret generated once and shared by every service that references it (use it for database passwords); \"$(OTHER)\" embeds an earlier variable of the same service, e.g. \"DATABASE_URL\": \"postgres://app:$(DB_PASSWORD)@db:5432/app\". Secrets from outside (API keys, OAuth client secrets, tokens) never go in the config, the source or the chat: the user adds them in the VibeDeploy dashboard (the site's Settings tab, section Secrets; get_app_status returns the direct link as secrets.manageUrl). Every service gets them as env vars and restarts automatically; an explicit env entry with the same name wins. get_app_status lists the secret names that are set, never their values. Volumes persist across deploys; everything else is recreated. For Postgres set PGDATA to a subdirectory of the volume. Outbound internet works (not SMTP port 25); private networks are blocked. Limits per site: 6 services, 2048Mi memory and 2000m CPU in total (default 256Mi / 500m per service), 4 volumes, 3Gi storage."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds what annotations convey: it discloses that services missing from the config are stopped but volumes/data are kept, that it blocks until every service is ready, that volumes persist while everything else is recreated, and details secrets handling, networking constraints, and per-site limits. This is rich behavioral context for a mutation tool.

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?

Front-loads the core action and the stopping/restarting caveat, then layers detail. Length is largely justified by the complex container config, though the config block is duplicated from the schema, which is wasted space.

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 a nested config object, no output schema, and 0 required parameters, the description covers return values (per-service status), failure handling, secret placement, volumes, and resource limits. An agent has what it needs to call it correctly.

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 coverage is only 33%; the config object is documented, but that text is duplicated verbatim in the schema and name/siteId receive no explanation in either place. The description compensates heavily for config but leaves the other two parameters undocumented, so it lands at the moderate baseline.

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+resource: 'Deploy or update the site's container services' with a clear scope (backend, database, Redis, workers, from any public image). The agent can distinguish this from generic deploy tools since it targets container services driven by an app config.

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 clear context: every call restarts services and picks up new source files, and it routes the agent to get_app_status with logs on failure. It does not, however, explicitly differentiate from sibling deploy tools such as deploy_site, build_and_deploy, or deploy_from_url.

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

All vibedeploy toolsInspect
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.

Resources