VibeKit

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

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

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

    How to connect

    How to connect VibeKit to Claude

    The server address to paste into Claude settings:

    https://mcp.vibekit.bot/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect VibeKit to ChatGPT

    The server address to paste into ChatGPT settings:

    https://mcp.vibekit.bot/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect VibeKit to Cursor

    The server address to paste into Cursor settings:

    https://mcp.vibekit.bot/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (36)

    Raw names from tools/list. Only developers need these.

    vibekit_list_appsList 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_get_appGet full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps.
    vibekit_create_appCreate 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.
    vibekit_list_templatesList 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_deployDeploy 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.
    vibekit_redeployRedeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.
    vibekit_app_logsFetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.
    vibekit_restart_appRestart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.
    vibekit_stop_appStop 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.
    vibekit_start_appStart a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.
    vibekit_app_envGet the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.
    vibekit_set_envSet or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.
    vibekit_delete_appPermanently 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.
    vibekit_chatSend 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.
    vibekit_agent_statusCheck 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.
    vibekit_agent_historyGet the recent chat history between the user and an app's AI agent.
    vibekit_enable_databaseProvision 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.
    vibekit_database_statusGet an app's database status and connection info (whether it's provisioned, frozen, etc.).
    vibekit_db_schemaGet an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.
    vibekit_db_queryRun 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.
    vibekit_db_tableBrowse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.
    vibekit_list_deploysList an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.
    vibekit_rollback_deployRoll 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.
    vibekit_run_qaKick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results.
    vibekit_qa_statusGet the latest automated QA results and status for an app.
    vibekit_submit_taskSubmit 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.
    vibekit_get_taskGet the status and result of a task submitted via vibekit_submit_task.
    vibekit_list_tasksList recent coding tasks, optionally filtered by status.
    vibekit_wait_for_taskBlock 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.
    vibekit_cancel_taskCancel a running task by taskId. No-op if it has already finished.
    vibekit_create_scheduleCreate 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.
    vibekit_list_schedulesList all of the account's scheduled recurring tasks.
    vibekit_delete_scheduleDelete a scheduled recurring task by scheduleId. Confirm with the user first.
    vibekit_accountGet VibeKit account info: plan, credit balance, and usage.
    vibekit_list_skillsList available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill.
    vibekit_get_skillFetch 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.