Add VibeKit MCP server (hosting + deployment)

[609NFT]

Adds VibeKit to the MCP servers directory. There is no Hosting/Deployment entry in the curated list yet, so this fills a gap rather than duplicating one.

What it does: deploy a GitHub repo or starter template to a live URL, tail logs, set env vars, attach Postgres, restart/stop apps, and message each app's built-in coding agent. 36 tools.

Verification (all live as of 2026-08-07):

• Hosted endpoint answers a standard handshake: POST https://mcp.vibekit.bot/mcp returns protocolVersion 2025-06-18, serverInfo {name: "vibekit", version: "0.8.0"}.
• Source is public and MIT: https://github.com/VibeKit-Bot/vibekit-mcp
• Also published to the official MCP registry as io.github.VibeKit-Bot/vibekit-mcp, and on npm as vibekit-mcp.
• docsUrl points at the setup page that explains how to get the vk_ key, per CONTRIBUTING's note for hosted servers with auth.

Disclosure: I work on VibeKit, so this is a self-submission. The description states the third-party-hosting trade-off plainly (apps run in VibeKit's containers, not on your own machine) rather than leaving it out.

Name collision worth flagging for the directory: there is an unrelated, discontinued superagent-ai/vibekit sandbox SDK that several tool directories list under the bare name "VibeKit". The description names the distinction so this entry does not compound that confusion.

npx tsc --noEmit clean and npm run build passes; /mcp-servers/vibekit prerenders.

[vercel]

@609NFT is attempting to deploy a commit to the Thomas McParland's projects Team on Vercel.

A member of the Team first needs to authorize it.