KitScout

Categories › Cloud & DevOps › Hosting & deployment

VibeDeploy

MCP serverVerified domain · vibedeploy.beRemote● LiveAPI key needed

Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.

Install

Remote server: your requests and data go to mcp.vibedeploy.be. Claude Code: claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do (first 40)

The tools this server listed when we connected to it, in its own words.

  • 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_cu
  • deploy_site — Publish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.g. {name}.subsite.site). A new name crea
  • update_site — Change files on an existing site. Default mode 'patch' writes only the listed files and keeps the rest; `delete: [paths]` removes files. mod
  • 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_
  • get_site — Return one site's details: live URL, status, plan, served file paths, whether editable source is stored (and its build settings), custom dom
  • 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);
  • 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 page
  • 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:'patc
  • 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 wit
  • 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 updat
  • 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
  • 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_e
  • 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 f
  • 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 t
  • 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_dep
  • delete_source_file — Remove one file from the site's editable source tree. The served files do not change until build_and_deploy runs.
  • 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
  • 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 targ
  • 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 comb
  • 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
  • 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
  • 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 (tar
  • 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) th
  • 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)
  • 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 mar
  • 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
  • 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
  • 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}.subsite.site).
  • 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_domai
  • list_dns_records — Read the DNS records VibeDeploy tracks for a site (host, type, value), oldest first, including custom-domain verification records. Read-only
  • check_domain_availability — Check whether a domain can be registered and get indicative prices (first year and the yearly price after it, VAT included where it applies)
  • 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)
  • 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 enc
  • 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' (abou
  • 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 f
  • 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.
  • 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 t
  • 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 de
  • 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 snapsho
  • 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 r

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools