VibeKit

Name: VibeKit
Author: VibeKit-Bot

MCP serverMCP

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

by VibeKit-Botrepository ↗homepage ↗v0.8.0MIT

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vibekit-bot-vibekit-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability113/113 checks ok

Tools observed via MCP handshake

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_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.
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 de
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 vali
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 G
vibekit_redeploy — Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.
vibekit_app_logs — Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.
vibekit_restart_app — Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.
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.
vibekit_start_app — Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.
vibekit_app_env — Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.
vibekit_set_env — Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.
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
vibekit_chat — 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'
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 in
vibekit_agent_history — Get the recent chat history between the user and an app's AI agent.
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/m
vibekit_database_status — Get an app's database status and connection info (whether it's provisioned, frozen, etc.).
vibekit_db_schema — Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.
vibekit_db_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/…)
vibekit_db_table — Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.
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.
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 forwa
vibekit_run_qa — Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results.
vibekit_qa_status — Get the latest automated QA results and status for an app.
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 vibeki
vibekit_get_task — Get the status and result of a task submitted via vibekit_submit_task.
vibekit_list_tasks — List recent coding tasks, optionally filtered by status.
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 f
vibekit_cancel_task — Cancel a running task by taskId. No-op if it has already finished.
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.
vibekit_list_schedules — List all of the account's scheduled recurring tasks.
vibekit_delete_schedule — Delete a scheduled recurring task by scheduleId. Confirm with the user first.
vibekit_account — Get VibeKit account info: plan, credit balance, and usage.
vibekit_list_skills — List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_ge
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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.VibeKit-Bot/vibekit-mcp

first seen 2 mo ago · fetched 2 d agoopen ↗

GitHub curated listsgithub.com/vibekit-bot/vibekit-mcp

first seen 2 mo ago · fetched 1 mo agoopen ↗

npm registryvibekit-mcp

first seen 2 mo ago · fetched 8 h agoopen ↗

Field history (12 recent events)

2 mo ago · declared · license → "MIT"
2 mo ago · observed · packageFacts → {"name":"vibekit-mcp","registry":"npm","publishedAt":"2026-07-17T16:58:21.032Z","latestVersion":"0.8.0","weeklyDownloads
2 mo ago · declared · summary → "Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client."
2 mo ago · declared · name → "VibeKit"
2 mo ago · declared · description → "Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client."
2 mo ago · declared · publisherName → "VibeKit-Bot"
2 mo ago · declared · homepageUrl → "https://vibekit.bot"
2 mo ago · declared · version → "0.8.0"
2 mo ago · declared · publisherName → "vibekit-bot"
2 mo ago · declared · publisherUrl → "https://github.com/vibekit-bot"
2 mo ago · declared · repoUrl → "https://github.com/VibeKit-Bot/vibekit-mcp"
2 mo ago · declared · protocols → ["mcp"]

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	126 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
11 h ago	mcp initialize	ok	200	330 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
18 h ago	mcp initialize	ok	200	320 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
24 h ago	mcp initialize	ok	200	306 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
31 h ago	mcp initialize	ok	200	331 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	324 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	359 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	341 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	321 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools
3 d ago	mcp initialize	ok	200	360 ms	server vibekit 0.8.0 · protocol 2025-06-18 · 36 tools

VibeKit

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from