Community · Official remote MCP server

The VibeKit MCP server,
connected in one click.

Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client. Connect the official VibeKit MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Free to start · No credit card · No hosting needed

What you can do

What your AI can do with VibeKit

Real prompts you can type the moment it's connected — no setup, no docs to read.

Use “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 ap.

Use “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.

Use “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 v.

Use “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_.

Security check

How secure is the VibeKit MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how VibeKit holds up.

F43/100

Security grade F

gate scanned 36 tools on Sep 4, 2026. A few things are worth a look before you connect.

  • mediumvibekit_restart_app: References secrets or data exfiltration
  • mediumvibekit_app_env: References secrets or data exfiltration
  • mediumvibekit_set_env: References secrets or data exfiltration
  • +4 more in the full report
Verified directory serverVibeKit · vibekit.bot

Official endpoint

Operated by VibeKit (vibekit.bot) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If VibeKit adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

How it works

Connected in three steps

01

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

02

Pick VibeKit

Choose VibeKit in the gate directory. No sign-in needed.

03

Use it anywhere

VibeKit's tools are live in every AI client you've connected — with rules and logging built in.

Connect VibeKit free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools VibeKit exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

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 ap

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 v

vibekit_list_templatesList the starter templates available to vibekit_create_app (e.g. landing, dashboard, blog, saas, crud-api). Call this before vibekit_create_

vibekit_deployDeploy a GitHub repo to VibeKit hosting, live at <subdomain>.vibekit.bot (Fargate container behind nginx, SSL automatic). Use when the code

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.

+ 28 more tools once connected

Server facts

The VibeKit MCP server at a glance

Endpointhttps://mcp.vibekit.bot/mcp
Operated byVibeKit (vibekit.bot)
CategoryCommunity
Sign-inNone — public data only
Available in gateYes — one-click connect
Works withClaude, ChatGPT, Cursor & any MCP client
FAQ

Questions, answered

Is there an official VibeKit MCP server?

Yes — VibeKit operates its own remote MCP server at mcp.vibekit.bot. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect VibeKit to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick VibeKit in the directory. No account or sign-in is needed. From then on, VibeKit's tools are available in every client you've connected to gate.

Do I need to host anything?

No. VibeKit runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the VibeKit MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.

Is it free?

Yes — you can get started with gate for free and connect VibeKit in minutes. No credit card required.

More servers

Connect more than just VibeKit

Every server below works through the same gateway URL — connect once, add tools anytime.

Set up VibeKit in: Claude · Claude Code · ChatGPT · Cursor · VS Code

Give your AI VibeKit — safely.

One URL. All MCPs. Full control. Free to start.

Get started free