INDIVIDUAL MCP TOOL
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.
LIVE ENDPOINT
https://mcp.vibedeploy.be/mcp
Connect to this endpoint to inspect the live schema for deploy_app and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vibedeploy]
url = "https://mcp.vibedeploy.be/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vibedeploy": {
"type": "http",
"url": "https://mcp.vibedeploy.be/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vibedeploy
Remote MCP URL: https://mcp.vibedeploy.be/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vibedeploy": {
"url": "https://mcp.vibedeploy.be/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vibedeploy": {
"type": "http",
"url": "https://mcp.vibedeploy.be/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vibedeploy",
"transport": "streamable-http",
"url": "https://mcp.vibedeploy.be/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_account— Return the team's plan, its limits, current usage, the trial end date and the per-token MCP rate limit.deploy_site— Publish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.update_site— Change files on an existing site.list_sites— List the team's sites (name, URL, status, last deploy), most recently updated first, up to 100.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.delete_site— Soft-delete a site (confirm:true required).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.read_file— Return one file the site serves now, as text (utf8) or base64 for binary files, e.