streamable-httpMITupdated 15d ago
MCP server for VibeKit, deploy apps, manage hosting, and chat with AI agents from any MCP client.
Was kannst du mit VibeKit machen?
vibekit-mcp
MCP server for VibeKit, deploy apps, manage hosting, and chat with AI agents from any MCP client.
This package is for VibeKit cloud/API access. It does not connect your local Claude Code instance to Telegram. For local-machine remote control, use vibekit-agent.
Use it remotely (no install)
VibeKit also runs as a hosted remote server, so clients that accept a remote MCP URL (claude.ai web connectors, ChatGPT, etc.) need no install:
https://mcp.vibekit.bot/mcp?api_key=vk_your_api_key_here
Paste that URL into your client's "custom connector" / "remote MCP server" field. Clients that let you set headers can instead send Authorization: Bearer vk_your_api_key_here and use the bare https://mcp.vibekit.bot/mcp. See Get an API key below.
Prefer a local stdio install (e.g. Claude Desktop)? Use the steps below.
Get an API key
Keys start with vk_. Two ways to get one:
- Instant, no signup: one request returns a key.
Save the returned key and reuse it. Each call tocurl -X POST https://vibekit.bot/api/v1/auth/register # Response: {"apiKey": "vk_...", "plan": "free", "credits": 0}/auth/registercreates a brand-new account, so call it once, not per request. - From your account: if you already use VibeKit, copy or regenerate your key in the web dashboard or the iOS app settings.
Installation
npm install -g vibekit-mcp
Setup
-
Get a VibeKit API key (see Get an API key above).
-
Add to your MCP client config (e.g. Claude Desktop) (
~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS):
{
"mcpServers": {
"vibekit": {
"command": "vibekit-mcp",
"env": {
"VIBEKIT_API_KEY": "vk_your_api_key_here"
}
}
}
}
- Restart your MCP client
Available Tools
Hosting
| Tool | Description |
|---|---|
vibekit_list_apps |
List all hosted apps |
vibekit_get_app |
Get details about a specific app |
vibekit_list_templates |
List starter templates for vibekit_create_app |
vibekit_create_app |
Create new app from a template |
vibekit_deploy |
Deploy GitHub repo to hosting |
vibekit_redeploy |
Redeploy app with latest code |
vibekit_list_deploys |
List an app's recent deploys with status and commit |
vibekit_rollback_deploy |
Roll an app back to a previous deploy |
vibekit_app_logs |
Get application logs |
vibekit_restart_app |
Restart an app |
vibekit_stop_app |
Stop an app |
vibekit_start_app |
Start a stopped app |
vibekit_app_env |
Get app environment variables |
vibekit_set_env |
Set app environment variables |
vibekit_delete_app |
Delete an app permanently |
Agent
| Tool | Description |
|---|---|
vibekit_chat |
Chat with an app's AI agent |
vibekit_agent_status |
Get agent status |
vibekit_agent_history |
Get chat history with agent |
Database
| Tool | Description |
|---|---|
vibekit_enable_database |
Enable a Postgres database for an app |
vibekit_database_status |
Get database status and connection info |
vibekit_db_schema |
Get the database schema (every table and its columns) |
vibekit_db_query |
Run a read-only SQL query (SELECT only, up to 200 rows) |
vibekit_db_table |
Browse one table's rows with pagination and sorting |
QA
| Tool | Description |
|---|---|
vibekit_run_qa |
Run automated QA tests |
vibekit_qa_status |
Get QA test results |
Tasks
| Tool | Description |
|---|---|
vibekit_submit_task |
Submit a coding task |
vibekit_get_task |
Get task status/result |
vibekit_list_tasks |
List recent tasks |
vibekit_wait_for_task |
Wait for task completion |
vibekit_cancel_task |
Cancel a running task |
vibekit_create_schedule |
Create recurring scheduled task |
vibekit_list_schedules |
List scheduled tasks |
vibekit_delete_schedule |
Delete scheduled task |
Account
| Tool | Description |
|---|---|
vibekit_account |
Get account info (plan, credits, usage) |
vibekit_list_skills |
List implementation skills |
vibekit_get_skill |
Fetch specific skill content |
Example Usage
Once configured, you can use prompts like:
- "Deploy my GitHub repo to VibeKit and create a new app"
- "Chat with the AI agent for my app about adding a contact form"
- "Show me the logs for my app and restart it if there are errors"
- "Enable a database for my app, then show me its schema and query the users table"
- "List my app's recent deploys and roll back to the last working one"
- "Run QA tests on my deployed app"
- "Check my VibeKit account balance and list my apps"
- "Create a weekly schedule to improve my app's performance"
Environment Variables
| Variable | Description | Default |
|---|---|---|
VIBEKIT_API_KEY |
Your VibeKit API key (required) | none |
VIBEKIT_API_URL |
API base URL | https://vibekit.bot/api/v1 |
Related Packages
vibekit-cli: terminal client for VibeKit cloud workflowsvibekit-agent: Telegram bridge for local Claude Code on your own machine
Links
- VibeKit Website
- API Documentation
- Dashboard (view or regenerate your API key)
- GitHub
Privacy Policy
VibeKit's privacy policy: https://vibekit.bot/privacy
What this MCP server does with your data, concretely:
- Every tool call is forwarded to the VibeKit API (
https://vibekit.bot/api/v1) over HTTPS, authenticated with the API key you configure. Tool inputs and outputs are processed by VibeKit to run your apps and agents, under the privacy policy above. - The server itself keeps no state: nothing is written to disk, no
analytics or telemetry are collected by this package, and your API key is
read from configuration (
VIBEKIT_API_KEY/ the extension's key field) and sent only tovibekit.bot. - Data retention, third-party sharing, and deletion are governed by the policy above. Questions: support@vibekit.bot.
Installation
VibeKit zu deinem Client hinzufügen. Wähl den, den du nutzt.
claude mcp add --transport http vibekit https://mcp.vibekit.bot/mcpcodex mcp add vibekit --url https://mcp.vibekit.bot/mcp{
"mcpServers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"vibekit": {
"type": "http",
"url": "https://mcp.vibekit.bot/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"vibekit": {
"url": "https://mcp.vibekit.bot/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"vibekit": {
"serverUrl": "https://mcp.vibekit.bot/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Unvollständig
- Dokumentation25/25
- Pflege25/25
- Vertrauen16/20
- Funktionsumfang0/15
- Installation12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 7 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Versionsverlauf
| Versionen | Veröffentlicht |
|---|---|
| 0.8.0Aktuell | 18. Juli 2026 |
| 0.7.5 | 17. Juli 2026 |
| 0.7.4 | 15. Juli 2026 |