VibeKit MCP server

• vibekit_accountFree

  Get VibeKit account info: plan, credit balance, and usage.

• vibekit_agent_historyFree

  Get the recent chat history between the user and an app's AI agent.

• vibekit_agent_statusFree

  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.

• vibekit_app_envFree

  Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.

• vibekit_app_logsFree

  Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.

• vibekit_cancel_taskwrite actionFree

  Cancel a running task by taskId. No-op if it has already finished.

• vibekit_chatwrite actionFree

  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.

• vibekit_create_appwrite actionFree

  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.

• vibekit_create_schedulewrite actionFree

  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_database_statusFree

  Get an app's database status and connection info (whether it's provisioned, frozen, etc.).

• vibekit_db_querywrite actionFree

  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.

• vibekit_db_schemaFree

  Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.

• vibekit_db_tableFree

  Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.

• vibekit_delete_appwrite actionFree

  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.

• vibekit_delete_schedulewrite actionFree

  Delete a scheduled recurring task by scheduleId. Confirm with the user first.

• vibekit_deploywrite actionFree

  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.

• vibekit_enable_databaseFree

  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.

• vibekit_get_appFree

  Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps.

• vibekit_get_skillFree

  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.

• vibekit_get_taskFree

  Get the status and result of a task submitted via vibekit_submit_task.

• vibekit_list_appsFree

  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_deploysFree

  List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.

• vibekit_list_schedulesFree

  List all of the account's scheduled recurring tasks.

• vibekit_list_skillsFree

  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_tasksFree

  List recent coding tasks, optionally filtered by status.

• vibekit_list_templatesFree

  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_statusFree

  Get the latest automated QA results and status for an app.

• vibekit_redeployFree

  Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.

• vibekit_restart_appFree

  Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.

• vibekit_rollback_deploywrite actionFree

  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.

• vibekit_run_qawrite actionFree

  Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results.

• vibekit_set_envFree

  Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.

• vibekit_start_appFree

  Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.

• vibekit_stop_appFree

  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_submit_taskwrite actionFree

  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.

• vibekit_wait_for_taskFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1107ms20/20
• Tool poisoning36 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 11 write-action tools with no auth3/15
• Maintenancelast push 11 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 55% of 1,119 Developer tools servers

Tools

36

the typical Developer tools server has 7

Tools that change things

31%

typical: 5%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Developer tools server answers 100%

Response time

113 ms

faster than 73% of 443 Developer tools servers

GitHub stars

1

more than 50% of 855 Developer tools servers

VibeKit: common questions

Is VibeKit MCP server safe?

Mostly: it is graded B (80/100). Read the VibeKit safety report

How do I install VibeKit?

It runs remotely at mcp.vibekit.bot. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does VibeKit need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is VibeKit maintained?

The last commit was 50 days ago (2026-09-15). The latest release is v0.8.0.

Is VibeKit up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of VibeKit?

Servers from other publishers that do the same job: Aiven MCP server, Nora MCP server and Edgegap MCP server. Compare all VibeKit alternatives.

How does VibeKit compare with other Developer tools MCP servers?

safety score 80/100 (higher than 55% of 1,119 Developer tools servers); tools 36 (the typical Developer tools server has 7); tools that change things 31% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.