List your agent

VibeDeploy

MCP server● Hosted · onlinev1.1.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used VibeDeploy? Be the first to help others choose.

What it does

VibeDeploy is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.1.0
PriceNot in the registry
First seen26 Sept 2026
Last checked19h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://mcp.vibedeploy.be/mcp streamable-http

In Claude Code: claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "vibedeploy": {
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE VibeDeploy answered an MCP connection on 15 Nov 2026 and introduced itself as vibedeploy 1.1.0 (MCP protocol 2025-06-18).

43 tools offered to AI assistants

  • 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 a plan limit instead of running into PLAN_LIMIT_EXCEEDED.
  • 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 creates the site. An existing name REPLACES EVERY FILE (files not in this call are deleted) and needs co
  • 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 every file not listed. Preview with dryRun:true. Use deploy_site instead to crea
  • 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 files, source status and history.
  • 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 the last 10 deploys. Use get_site to inspect a site before editing it; use list_
  • 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 can restore it in the VibeDeploy dashboard. Use delete_site to remove the whole
  • 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, device/browser breakdowns, and Web Vitals averages. Never exposes raw visitor IPs o
  • 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 for the served files; use read_source_file instead for the editable source tree (g
  • 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_EXCEEDED, so request them again in another call. Use read_source_files instead for th
  • 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' or begin_deploy plus add_files.
  • 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 source tree returns SOURCE_NOT_STORED: write the source with write_source_files, or
  • 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') and build_and_deploy. The served files do not change, and a site that already
Show 31 more
  • 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_files shows the paths. Use read_source_file for source; use read_file instead for
  • 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 BATCH_BUDGET_EXCEEDED. Use read_source_files for source; use read_files instead
  • 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_source_files first to see what exists. A legacy site without source storage retur
  • 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 served files (a restore point is normally taken first). Use build_and_deploy after changing stored s
  • 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 before reading files in bulk, to find the ones that matter.
  • 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_from_url when the files are already published at a public URL, such as a repositor
  • 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 the HTML <img> references to local paths so the site no longer depends on the ori
  • 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 expects; any mismatch aborts the call with no writes. Served-file (dist) edits go l
  • 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', shipped by build_and_deploy). Same edit rules as update_file_content. All or nothing:
  • 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 publish and their verification status. The submission format for the site's form is
  • 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-To, and full email branding (subject template, field labels/order, logo, accent
  • 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 relay sends from the custom From (DKIM-signed). Until then it falls back to the
  • 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, plus a TXT that proves ownership). Idempotent: the same siteName and domain ret
  • 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 certificate follows automatically, usually within a minute or two. If it fails, t
  • 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_domain or remove_custom_domain) and those linked in the VibeDeploy dashboard (source 'dashboard', verifie
  • 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, changes or deletes a DNS record.
  • 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). Read-only: it never buys, registers or reserves a domain. alternatives:true also checks the same n
  • 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 returned uploadUrl, then publish with commit_deploy. Use begin_deploy only when the fil
  • 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 on every call. A 100-250 KB text file usually fits in one call with encoding:'gzi
  • 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 one call), begin_deploy's uploadUrl (one 100 MB tar POST) or deploy_from_url (pu
  • 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 stays open to retry or abort). Replace mode on a site that has files needs confir
  • 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 to commit or abort leftovers.
  • 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 snapshot holds the content from BEFORE that entry. Restoring is done by the use
  • 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 user in the VibeDeploy dashboard within the plan's restore window.
  • 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. Served content does not change, but retention cleanup may remove older snapshots. Con
  • 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 MySQL, Redis, or workers, each in a gVisor sandbox. The call applies the whole co
  • 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 that are set (never values) with the dashboard link where the user adds them, the
  • 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 for good. Use remove_app to stop only the containers; use delete_site to remove

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.vibedeploy.be/mcpDECLAREDSRC-001 Official MCP Registry19h ago
Websitehttps://vibedeploy.be/mcpDECLAREDSRC-001 Official MCP Registry19h ago
Version1.1.0DECLAREDSRC-001 Official MCP Registry19h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry19h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry19h ago
Repositoryhttps://github.com/thomasbillen-netizen/vibedeploy-mcpDECLAREDSRC-001 Official MCP Registry19h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry19h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry19h ago

Change history

  • VERSION14 Oct 2026
    1.0.1 → 1.1.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run VibeDeploy? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor VibeDeployLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of VibeDeploy?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/vibedeploy?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/vibedeploy/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about VibeDeploy

How do I connect VibeDeploy?

Use the hosted endpoint https://mcp.vibedeploy.be/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does VibeDeploy offer?

When Electra Index connected on 15 Nov 2026, it listed 43 tools: get_account, deploy_site, update_site, list_sites, get_site, delete_site, get_site_analytics, read_file and more. The full list is in "Live check" above.

Is VibeDeploy online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use VibeDeploy for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.