mcp server
VibeKit
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
Description as published by the maintainer. Source
- version 0.8.0
- active
active — Registry entry last updated 2026-07-18.
What this server can do
36 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
vibekit_account- Get VibeKit account info: plan, credit balance, and usage.
vibekit_agent_history(appId, limit)- Get the recent chat history between the user and an app's AI agent. Required: appId.
vibekit_agent_status(appId)- Check whether an app's AI agent is idle or working, and get its LIVE progress. Returns activity.status = the current human-readable build step (e.g. 'editing index.html', 'deploying'), activity.steps = the steps so far, and activity.done = whether the turn finished. Poll this every few seconds while a build is running and relay activity.status to the user so they see progress. Once activity.done is true the response also includes liveCheck = a server-side fetch of the deployed page ({ url, ok, httpStatus, title }); use it to confirm the app is live and renders — do NOT curl/fetch the URL yourself, your sandbox may block it. Required: appId.
vibekit_app_env(appId)- Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them. Required: appId.
vibekit_app_logs(appId, lines)- Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving. Required: appId.
vibekit_cancel_task(taskId)- Cancel a running task by taskId. No-op if it has already finished. Required: taskId.
vibekit_chat(appId, message)- Send a message to an app's built-in AI coding agent, which reads, writes, and modifies the app's code and redeploys it. Use for 'build/make a change to my app' requests. If the agent finishes quickly you get its reply directly. Otherwise you get status:'working' — do NOT resend; instead give the user LIVE progress: poll vibekit_agent_status every few seconds and relay the current step from activity.status ('editing the homepage…', 'deploying…') until activity.done, then read vibekit_agent_history for the final reply. Required: appId, message.
vibekit_create_app(template, subdomain)- Create a new hosted app from a starter template and deploy it live at <subdomain>.vibekit.bot. Call vibekit_list_templates first to pick a valid template. To deploy existing code from a GitHub repo instead, use vibekit_deploy. Required: template, subdomain.
vibekit_create_schedule(cron, name, repo, task)- Create a recurring coding task that the AI runs automatically on a cron schedule (e.g. a weekly SEO pass). Use for 'every Monday, do X to my repo' requests. Required: task, repo, cron.
vibekit_database_status(appId)- Get an app's database status and connection info (whether it's provisioned, frozen, etc.). Required: appId.
vibekit_db_query(sql, appId)- Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars. Required: appId, sql.
vibekit_db_schema(appId)- Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query. Required: appId.
vibekit_db_table(appId, limit, table, offset)- Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT. Required: appId, table.
vibekit_delete_app(appId)- Permanently delete a hosted app — stops the container and removes its workspace, database, env vars, and subdomain. Irreversible (the GitHub repo is NOT touched). Confirm with the user before calling. Required: appId.
vibekit_delete_schedule(scheduleId)- Delete a scheduled recurring task by scheduleId. Confirm with the user first. Required: scheduleId.
vibekit_deploy(repo, subdomain)- Deploy a GitHub repo to VibeKit hosting, live at <subdomain>.vibekit.bot (Fargate container behind nginx, SSL automatic). Use when the code already lives in a GitHub repo; for a starter template instead use vibekit_create_app. Required: repo, subdomain.
vibekit_enable_database(appId)- Provision a Postgres database for an app (idempotent — safe if already enabled). Required before the vibekit_db_* tools work. Note: free-tier apps need the $3/mo Database add-on. Required: appId.
vibekit_get_app(appId)- Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps. Required: appId.
vibekit_get_skill(id)- Fetch the full content of a specific skill — implementation patterns, code examples, and best practices for a domain. Fetch on-demand when you need guidance on a specific topic. Required: id.
vibekit_get_task(taskId)- Get the status and result of a task submitted via vibekit_submit_task. Required: taskId.
vibekit_list_apps- List all hosted apps in your VibeKit account, each with its id, subdomain, status, and live URL. Start here to get an appId for the other app tools.
vibekit_list_deploys(appId, limit)- List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy. Required: appId.
vibekit_list_schedules- List all of the account's scheduled recurring tasks.
vibekit_list_skills(tag)- List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill.
vibekit_list_tasks(limit, status)- List recent coding tasks, optionally filtered by status.
vibekit_list_templates- List the starter templates available to vibekit_create_app (e.g. landing, dashboard, blog, saas, crud-api). Call this before vibekit_create_app to choose a valid template.
vibekit_qa_status(appId)- Get the latest automated QA results and status for an app. Required: appId.
vibekit_redeploy(appId)- Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo. Required: appId.
vibekit_restart_app(appId)- Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables. Required: appId.
vibekit_rollback_deploy(appId, deployId)- Roll an app back to a previous deploy (get the deployId from vibekit_list_deploys). The container restarts on the rolled-back build; reversible by rolling forward again. Required: appId, deployId.
vibekit_run_qa(appId)- Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results. Required: appId.
vibekit_set_env(vars, appId)- Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect. Required: appId, vars.
vibekit_start_app(appId)- Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online. Required: appId.
vibekit_stop_app(appId)- Stop a hosted app's container. The app stays in your account and can be brought back with vibekit_start_app. Use to take an app offline without deleting it. Required: appId.
vibekit_submit_task(repo, task, branch, deploy, callbackUrl)- Submit an autonomous coding task. The AI writes the code, commits to GitHub, and (by default) deploys to <subdomain>.vibekit.bot. Returns a taskId — poll vibekit_get_task or block with vibekit_wait_for_task. Use for 'build X' or 'change X' work against a repo. Required: task.
vibekit_wait_for_task(taskId, timeoutSeconds)- Block until a submitted task finishes (or the timeout), polling every 5 seconds, then return its result. Use right after vibekit_submit_task when you want the final result inline. Required: taskId.
Last successful function declaration observed on . Source: https://mcp.vibekit.bot/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.vibekit.bot/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.8.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-18 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-18 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 36 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.vibekit.bot | |
| mcp endpoint status | ok | The server listed 36 functions when asked. | as of probe | mcp.vibekit.bot |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json