# VibeKit MCP server

Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-vibekit-bot-vibekit-mcp
- Repository: https://github.com/VibeKit-Bot/vibekit-mcp
- Website: https://vibekit.bot

## Install
- Endpoint: https://mcp.vibekit.bot/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.vibekit.bot/mcp

## Tools
- vibekit_list_apps (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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_get_app (VibeKit Get App) - Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_create_app (VibeKit Create App) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_list_templates (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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_deploy (VibeKit Deploy) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_redeploy (VibeKit Redeploy) - Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_app_logs (VibeKit App Logs) - Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_restart_app (VibeKit Restart App) - Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_stop_app (VibeKit Stop App) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_start_app (VibeKit Start App) - Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_app_env (VibeKit Get Env Vars) - Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_set_env (VibeKit Set Env Vars) - Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_delete_app (VibeKit Delete App) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_chat (VibeKit Chat with Agent) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_agent_status (VibeKit Agent Status) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_agent_history (VibeKit Agent History) - Get the recent chat history between the user and an app's AI agent. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_enable_database (VibeKit Enable Database) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_database_status (VibeKit Database Status) - Get an app's database status and connection info (whether it's provisioned, frozen, etc.). Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_db_schema (VibeKit Database Schema) - Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_db_query (VibeKit Run SQL Query) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_db_table (VibeKit Browse Table) - Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_list_deploys (VibeKit List Deploys) - List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_rollback_deploy (VibeKit Rollback Deploy) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_run_qa (VibeKit Run QA) - Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_qa_status (VibeKit QA Status) - Get the latest automated QA results and status for an app. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_submit_task (VibeKit Submit Task) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_get_task (VibeKit Get Task) - Get the status and result of a task submitted via vibekit_submit_task. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_list_tasks (VibeKit List Tasks) - List recent coding tasks, optionally filtered by status. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_wait_for_task (VibeKit Wait for Task) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_cancel_task (VibeKit Cancel Task) - Cancel a running task by taskId. No-op if it has already finished. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_create_schedule (VibeKit Create Schedule) - 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. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_list_schedules (VibeKit List Schedules) - List all of the account's scheduled recurring tasks. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_delete_schedule (VibeKit Delete Schedule) - Delete a scheduled recurring task by scheduleId. Confirm with the user first. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_account (VibeKit Account Info) - Get VibeKit account info: plan, credit balance, and usage. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_list_skills (VibeKit List Skills) - List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill. Endpoint: https://mcp.vibekit.bot/mcp
- vibekit_get_skill (VibeKit Get Skill) - 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. Endpoint: https://mcp.vibekit.bot/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.VibeKit-Bot
- Version: 0.8.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 18, 2026
- Source: https://registry.modelcontextprotocol.io