# Vibedeploy MCP server

Source: https://glimind.com/server/mcp-registry%2Fbe.vibedeploy%2Fvibedeploy
Registry id: `mcp-registry/be.vibedeploy/vibedeploy`
Status: live (checked 2026-10-27T04:10:03.302Z)

## Verdict

Vibedeploy MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 40% of MCP servers, with 861 ms median handshake and 9 outages in 90 days. Its agent-readiness grade is A (91/100) across 43 tools, costing an agent about 13,323 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 40% of MCP servers |
| Median handshake latency | 861 ms | 24% of MCP servers |
| p95 handshake latency | 3220 ms | — |
| Checks in 30 days | 4,983 | — |
| Outages, 90 days | 9 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 91/100 (A) | 71% of MCP servers |
| Tools | 43 | — |
| Tool-list size for an agent | ~13,323 tokens | 15% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "vibedeploy-mcp-server": {
      "type": "http",
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http vibedeploy-mcp-server https://mcp.vibedeploy.be/mcp
```

## Tools (43)

- `abort_deploy`: Discard a begin_deploy session and its staged files; the live site is untouched. Cleanup is best effort and retried later if it fails.
- `add_custom_domain`: Start attaching a user-owned domain to an existing site: returns the DNS records the user adds at their DNS provider (a routing record that sends visitors here,
- `add_file_chunk`: Send one file in several calls when it is too big for a single tool call. Last resort: first try add_files with encoding:'gzip+base64' (about 250 KB of text in 
- `add_files`: 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 o
- `apply_edits`: Apply literal find/replace edits to several files in one call, in the served files (target 'dist', live at once) or the editable source (target 'source', shippe
- `begin_deploy`: Open a staging session for a deploy that is too large for one call: stage files with add_files (repeatable), add_file_chunk, or one tar(.gz) POST to the returne
- `build_and_deploy`: Build the site's stored editable source in an isolated one-shot build pod and atomically publish the output as the live site, replacing the served files (a rest
- `check_domain_availability`: Check whether a domain can be registered and get an indicative price (VAT included where it applies). Read-only: it never buys, registers or reserves a domain. 
- `commit_deploy`: Publish a begin_deploy session's staged files to the live site in one atomic step, after a secret and malware scan of the complete set (on failure the session s
- `create_snapshot`: Take a point-in-time snapshot of a site's served files, a restore point the user can restore in the VibeDeploy dashboard within the plan's restore window. Serve
- `delete_site`: Soft-delete a site (confirm:true required). It stops serving at once and is purged after the plan's restore window (purgesAt in the result); until then the user
- `delete_source_file`: Remove one file from the site's editable source tree. The served files do not change until build_and_deploy runs.
- `deploy_app`: Run container services next to a site, from any public image: the user's own server (running code from the site's source tree), a database such as Postgres or M
- `deploy_from_url`: Fetch a public tar(.gz) archive over HTTPS and deploy its files to an existing site in one call (begin_deploy, upload and commit_deploy combined). Use deploy_fr
- `deploy_site`: Publish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.g. {name}.vibedeploy.be). A new name creates the site. An ex
- `get_account`: Return the team's plan, its limits, current usage, the trial end date and the per-token MCP rate limit. Call it before deploy_site or add_custom_domain to check
- `get_app_status`: Show the site's container services: per-service status (ready, restarts, waiting or crash reasons, volumes), the stored config, the names of the site secrets th
- `get_forms_config`: Read the form-to-email relay config of a site, plus the resolved delivery mode, the active From address, and (for a custom sender domain) the DNS records to pub
- `get_site`: Return one site's details: live URL, status, plan, served file paths, whether editable source is stored (and its build settings), custom domains, bandwidth and 
- `get_site_analytics`: Return a privacy-safe traffic summary for a site over the last `period` days (default 7): total page views, distinct-visitor count, top pages, daily counts, dev
- `list_custom_domains`: Return all custom domains attached to a site, both those added with add_custom_domain (source 'mcp', with a recordId for verify_custom_domain or remove_custom_d
- `list_deploys`: List the team's begin_deploy staging sessions, by default the active ones (open and committing), up to 50. Useful after a crash or restart to commit or abort le
- `list_dns_records`: Read the DNS records VibeDeploy tracks for a site (host, type, value), oldest first, including custom-domain verification records. Read-only: it never creates, 
- `list_file_hashes`: Return SHA-256 and size of every served file. Before a redeploy, hash your local files, compare, and upload only the changed ones with update_site mode:'patch' 
- `list_history`: Return the site's last 50 deploy and snapshot entries, newest first: how each was triggered, label, snapshot name, file count and secrets detected. Each entry's
- `list_sites`: List the team's sites (name, URL, status, last deploy), most recently updated first, up to 100. Use list_sites to find a site name; use get_site for one site's 
- `list_snapshots`: List the snapshots of a site's served files (point-in-time restore points). NO_VOLUME means the site was never deployed. Restoring a snapshot is done by the use
- `list_source_files`: List path, SHA-256 and size of every file in the site's editable source tree (the stored pre-build code, not the served files). Read-only. A site without a sour
- `promote_dist_to_source`: Create the editable source tree of a site that has none by copying the files it serves, so later changes can use write_source_files, apply_edits(target:'source'
- `read_file`: Return one file the site serves now, as text (utf8) or base64 for binary files, e.g. to edit it and send it back with update_site mode:'patch'. Use read_file fo
- `read_files`: Read up to 50 served files in one call, with the same per-file rules as read_file and 8388608 bytes in total; paths past the budget fail with BATCH_BUDGET_EXCEE
- `read_source_file`: Return one file from the site's editable source tree (the stored pre-build code), so any chat can edit the site without the original local files. list_source_fi
- `read_source_files`: Read up to 50 files from the editable source tree in one call (8388608 bytes in total). Each path succeeds or fails on its own; paths past the budget fail with 
- `rehost_images`: Download the external images a site references (e.g. from the old site it was rebuilt from), store them on this VibeDeploy site under assets/img/, and rewrite t
- `remove_app`: Stop every container service of the site; the site serves its static files again. Volumes (database data) are kept unless deleteData is true, which deletes them
- `remove_custom_domain`: Detach a custom domain from a site. The site itself is unaffected and keeps serving on its platform subdomain (e.g. {name}.vibedeploy.be).
- `search_files`: Search every file of a site for a literal string or a regular expression: the served files by default, or the editable source tree with target 'source'. Use it 
- `set_forms_config`: Configure the built-in form-to-email relay, fully self-service. Supports a custom From (via a verified sender domain or your own SMTP relay), an explicit Reply-
- `update_file_content`: Apply literal find/replace edits to one file in one call, for small changes where uploading the whole file is wasteful. Each edit states how many matches it exp
- `update_site`: Change files on an existing site. Default mode 'patch' writes only the listed files and keeps the rest; `delete: [paths]` removes files. mode:'replace' deletes 
- `verify_custom_domain`: Check the records from add_custom_domain (the ownership TXT and the routing record) and, when both are right, start serving the site on that domain; the HTTPS c
- `verify_forms_sender_domain`: Check the DNS records for a site's custom sender domain (DKIM TXT + SPF include). Once the DKIM record is observed, the sender domain is marked verified and the
- `write_source_files`: Write or overwrite files in the site's editable source tree (the first write creates it). The served files do not change until build_and_deploy runs. Use list_s

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.