VibeKit is a remote MCP server that gives an AI agent 36 tools, among them vibekit_account, vibekit_agent_history, vibekit_agent_status. It answers at https://mcp.vibekit.bot/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
vibekit_account | Get VibeKit account info: plan, credit balance, and usage. |
vibekit_agent_history | Get the recent chat history between the user and an app's AI agent. Inputs: appId, limit |
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 = Inputs: appId |
vibekit_app_env | Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them. Inputs: appId |
vibekit_app_logs | Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving. Inputs: appId, lines |
vibekit_cancel_task | Cancel a running task by taskId. No-op if it has already finished. Inputs: taskId |
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' requests. If the agent finishes quickly you get its reply directly. Otherwise yo Inputs: appId, message |
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. Inputs: template, subdomain |
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. Inputs: task, repo, cron, name |
vibekit_database_status | Get an app's database status and connection info (whether it's provisioned, frozen, etc.). Inputs: appId |
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/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the ag Inputs: appId, sql |
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. Inputs: appId |
vibekit_db_table | Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT. Inputs: appId, table, limit, offset |
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. Inputs: appId |
vibekit_delete_schedule | Delete a scheduled recurring task by scheduleId. Confirm with the user first. Inputs: scheduleId |
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. Inputs: repo, subdomain |
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. Inputs: appId |
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. Inputs: appId |
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. Inputs: id |
vibekit_get_task | Get the status and result of a task submitted via vibekit_submit_task. Inputs: 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 | List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy. Inputs: appId, limit |
vibekit_list_schedules | List all of the account's scheduled recurring tasks. |
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. Inputs: tag |
vibekit_list_tasks | List recent coding tasks, optionally filtered by status. Inputs: limit, 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 | Get the latest automated QA results and status for an app. Inputs: appId |
vibekit_redeploy | Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo. Inputs: appId |
vibekit_restart_app | Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables. Inputs: appId |
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. Inputs: appId, deployId |
vibekit_run_qa | Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results. Inputs: appId |
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. Inputs: appId, vars |
vibekit_start_app | Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online. Inputs: appId |
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. Inputs: appId |
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' Inputs: task, repo, branch, deploy, callbackUrl |
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. Inputs: taskId, timeoutSeconds |
Every block below points at https://mcp.vibekit.bot/mcp. Pick your client and copy.
claude mcp add --transport http vibekit https://mcp.vibekit.bot/mcp
{
"mcpServers": {
"vibekit": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.vibekit.bot/mcp"]
}
}
}{
"mcpServers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}{
"servers": {
"vibekit": {
"type": "http",
"url": "https://mcp.vibekit.bot/mcp"
}
}
}{
"context_servers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}{
"mcpServers": {
"vibekit": {
"serverUrl": "https://mcp.vibekit.bot/mcp"
}
}
}{
"mcpServers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}name: VibeKit
version: 0.0.1
schema: v1
mcpServers:
- name: VibeKit
type: streamable-http
url: https://mcp.vibekit.bot/mcp{
"mcpServers": {
"vibekit": {
"httpUrl": "https://mcp.vibekit.bot/mcp"
}
}
}{
"mcpServers": {
"vibekit": {
"type": "http",
"url": "https://mcp.vibekit.bot/mcp"
}
}
}{
"mcpServers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.vibekit.bot%2Fmcp&type=streamable_http&id=vibekit&name=VibeKit
It answered our last check on 21 October 2026 in 395 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
36, as returned by the server's own tools/list on 13 September 2026: vibekit_account, vibekit_agent_history, vibekit_agent_status, vibekit_app_env, vibekit_app_logs, vibekit_cancel_task, vibekit_chat, vibekit_create_app, and 28 more.
It answered our last check on 21 October 2026 in 395 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.vibekit.bot/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.vibekit-bot. Endpoint host: mcp.vibekit.bot. ARD identifier: urn:air:io.github.vibekit-bot:mcp:vibekit-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.