Skip to main content
Glama
Sign In
deenesjakoruzh
VibeKit MCP

VibeKit MCP

by VibeKit-Bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibekit-mcp

用于 VibeKit 的 MCP 服务器，可从任何 MCP 客户端部署应用、管理托管并与 AI 代理聊天。

此包用于 VibeKit 云/API 访问。它不会将你的本地 Claude Code 实例连接到 Telegram。如需本地机器远程控制，请使用 vibekit-agent。

远程使用（无需安装）

VibeKit 也作为托管远程服务器运行，因此接受远程 MCP URL 的客户端（claude.ai 网络连接器、ChatGPT 等）无需安装：

https://mcp.vibekit.bot/mcp?api_key=vk_your_api_key_here

将该 URL 粘贴到客户端的“自定义连接器”/“远程 MCP 服务器”字段中。允许设置请求头的客户端可以改为发送 Authorization: Bearer vk_your_api_key_here，并使用裸地址 https://mcp.vibekit.bot/mcp。请参阅下面的获取 API 密钥。

更喜欢本地 stdio 安装（例如 Claude Desktop）？请使用以下步骤。

Related MCP server: vibekit-mcp

获取 API 密钥

密钥以 vk_ 开头。有两种获取方式：

  • 即时获取，无需注册： 一次请求即可返回密钥。

    curl -X POST https://vibekit.bot/api/v1/auth/register
# Response: {"apiKey": "vk_...", "plan": "free", "credits": 0}

    保存返回的密钥并重复使用。每次调用 /auth/register 都会创建一个全新账户，因此请只调用一次，而不是每次请求都调用。

  • 从你的账户获取： 如果你已经在使用 VibeKit，可以在网页仪表盘或 iOS 应用设置中复制或重新生成密钥。

安装

npm install -g vibekit-mcp

设置

  1. 获取 VibeKit API 密钥（请参阅上面的获取 API 密钥）。

  2. 添加到你的 MCP 客户端配置（例如 Claude Desktop）（macOS 上为 ~/Library/Application Support/Claude/claude_desktop_config.json）：

{
  "mcpServers": {
    "vibekit": {
      "command": "vibekit-mcp",
      "env": {
        "VIBEKIT_API_KEY": "vk_your_api_key_here"
      }
    }
  }
}

  1. 重启你的 MCP 客户端

可用工具

托管

工具

描述

vibekit_list_apps

列出所有托管应用

vibekit_get_app

获取特定应用的详细信息

vibekit_list_templates

列出 vibekit_create_app 的入门模板

vibekit_create_app

从模板创建新应用

vibekit_deploy

将 GitHub 仓库部署到托管

vibekit_redeploy

使用最新代码重新部署应用

vibekit_list_deploys

列出应用最近的部署，包含状态和提交

vibekit_rollback_deploy

将应用回滚到之前的部署

vibekit_app_logs

获取应用日志

vibekit_restart_app

重启应用

vibekit_stop_app

停止应用

vibekit_start_app

启动已停止的应用

vibekit_app_env

获取应用环境变量

vibekit_set_env

设置应用环境变量

vibekit_delete_app

永久删除应用

代理

工具

描述

vibekit_chat

与应用的人工智能代理聊天

vibekit_agent_status

获取代理状态

vibekit_agent_history

获取与代理的聊天记录

数据库

工具

描述

vibekit_enable_database

为应用启用 Postgres 数据库

vibekit_database_status

获取数据库状态和连接信息

vibekit_db_schema

获取数据库架构（每个表及其列）

vibekit_db_query

运行只读 SQL 查询（仅 SELECT，最多 200 行）

vibekit_db_table

浏览一个表的行，支持分页和排序

QA

工具

描述

vibekit_run_qa

运行自动化 QA 测试

vibekit_qa_status

获取 QA 测试结果

任务

工具

描述

vibekit_submit_task

提交编码任务

vibekit_get_task

获取任务状态/结果

vibekit_list_tasks

列出最近的任务

vibekit_wait_for_task

等待任务完成

vibekit_cancel_task

取消正在运行的任务

vibekit_create_schedule

创建重复计划任务

vibekit_list_schedules

列出计划任务

vibekit_delete_schedule

删除计划任务

账户

工具

描述

vibekit_account

获取账户信息（计划、积分、使用量）

vibekit_list_skills

列出实现技能

vibekit_get_skill

获取特定技能内容

示例用法

配置完成后，你可以使用如下提示：

  • “将我的 GitHub 仓库部署到 VibeKit 并创建一个新应用”

  • “与我的应用的人工智能代理聊天，讨论添加联系表单”

  • “显示我的应用日志，如果有错误则重启它”

  • “为我的应用启用数据库，然后显示其架构并查询用户表”

  • “列出我的应用最近的部署，并回滚到最后一个可用的”

  • “对我的已部署应用运行 QA 测试”

  • “检查我的 VibeKit 账户余额并列出我的应用”

  • “创建每周计划以提升我的应用性能”

环境变量

变量

描述

默认值

VIBEKIT_API_KEY

你的 VibeKit API 密钥（必需）

无

VIBEKIT_API_URL

API 基础 URL

https://vibekit.bot/api/v1

相关包

  • vibekit-cli：用于 VibeKit 云工作流的终端客户端

  • vibekit-agent：用于你自己机器上本地 Claude Code 的 Telegram 桥接

链接

隐私政策

VibeKit 的隐私政策：https://vibekit.bot/privacy

此 MCP 服务器具体如何处理你的数据：

  • 每次工具调用都会通过 HTTPS 转发到 VibeKit API（https://vibekit.bot/api/v1），并使用你配置的 API 密钥进行身份验证。工具输入和输出由 VibeKit 处理，以运行你的应用和代理，并受上述隐私政策约束。

  • 服务器本身不保留任何状态：不会向磁盘写入任何内容，此包不收集任何分析或遥测数据，你的 API 密钥从配置（VIBEKIT_API_KEY / 扩展的密钥字段）中读取，并且仅发送到 vibekit.bot。

  • 数据保留、第三方共享和删除均受上述政策约束。如有疑问：support@vibekit.bot。

Available Tools

2 tools
vibekit_database_statusVibeKit Database StatusA
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault
appIdYesApp ID (from vibekit_list_apps)

Output Schema

NameRequiredDescription
okYesWhether the call succeeded.
dataNoDatabase stats: tables, storage, and connection info.
errorNoError message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint. The description adds minimal behavioral context (e.g., 'whether it's provisioned, frozen, etc.') but does not reveal additional traits. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. Every element is purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not explain return values. It covers the essential purpose and mentions example states. Could be slightly more specific but is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a description for 'appId'. The tool description adds no extra meaning beyond the schema, so baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get an app's database status and connection info', which uses the verb 'Get' and specifies the resource. It distinguishes from siblings like 'vibekit_db_query' and 'vibekit_enable_database' by focusing solely on status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description only states what it does, leaving the agent to infer context from sibling tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

vibekit_get_taskVibeKit Get TaskA
Read-only
Inspect

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

NameRequiredDescriptionDefault
taskIdYesTask ID returned from vibekit_submit_task

Output Schema

NameRequiredDescription
okYesWhether the call succeeded.
dataNoTask details: status, logs/result summary, and repo info.
errorNoError message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already set readOnlyHint=true, indicating no side effects. The description adds no further behavioral details (e.g., re-fetch behavior, error states). With annotations covering safety, the description meets the baseline but does not exceed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that directly conveys the purpose without fluff. Every word is necessary; no redundancy or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description doesn't need to detail return values. The one-parameter tool is fully covered by the description and schema, leaving no gaps for an agent to misinterpret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with description for taskId. The description adds value by specifying that the ID comes from vibekit_submit_task, linking the tools together and clarifying the parameter's origin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'status and result of a task', and distinguishes it from sibling tools like vibekit_submit_task (creates) and vibekit_cancel_task (cancels). It references the specific submission tool, making purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use after vibekit_submit_task. It does not explicitly mention when not to use or alternatives like vibekit_wait_for_task for polling, but the context is clear enough for an agent to infer appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 31 tool updatesv0.7.5
    • Removedvibekit_account
    • Removedvibekit_agent_history
    • Removedvibekit_agent_status
    • Removedvibekit_app_env
    • Removedvibekit_app_logs
    • Removedvibekit_cancel_task
    • Removedvibekit_chat
    • Removedvibekit_create_app
    • Removedvibekit_create_schedule
    • Changedvibekit_database_status2 fields changed
      • changedInput schema / properties / appId / description
        Previous value: -"The app ID to get database status for"New value: +"App ID (from vibekit_list_apps)"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "Database stats: tables, storage, and connection info."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
    • Removedvibekit_delete_app
    • Removedvibekit_delete_schedule
    • Removedvibekit_deploy
    • Removedvibekit_enable_database
    • Removedvibekit_get_app
    • Removedvibekit_get_skill
    • Changedvibekit_get_task2 fields changed
      • changedInput schema / properties / taskId / description
        Previous value: -"The task ID returned from vibekit_submit_task"New value: +"Task ID returned from vibekit_submit_task"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "Task details: status, logs/result summary, and repo info."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
    • Removedvibekit_list_apps
    • Removedvibekit_list_schedules
    • Removedvibekit_list_skills
    • Removedvibekit_list_tasks
    • Removedvibekit_list_templates
    • Removedvibekit_qa_status
    • Removedvibekit_redeploy
    • Removedvibekit_restart_app
    • Removedvibekit_run_qa
    • Removedvibekit_set_env
    • Removedvibekit_start_app
    • Removedvibekit_stop_app
    • Removedvibekit_submit_task
    • Removedvibekit_wait_for_task
  2. 31 tool updatesv0.6.1
    • First observedvibekit_account
    • First observedvibekit_agent_history
    • First observedvibekit_agent_status
    • First observedvibekit_app_env
    • First observedvibekit_app_logs
    • First observedvibekit_cancel_task
    • First observedvibekit_chat
    • First observedvibekit_create_app
    • First observedvibekit_create_schedule
    • First observedvibekit_database_status
    • First observedvibekit_delete_app
    • First observedvibekit_delete_schedule
    • First observedvibekit_deploy
    • First observedvibekit_enable_database
    • First observedvibekit_get_app
    • First observedvibekit_get_skill
    • First observedvibekit_get_task
    • First observedvibekit_list_apps
    • First observedvibekit_list_schedules
    • First observedvibekit_list_skills
    • First observedvibekit_list_tasks
    • First observedvibekit_list_templates
    • First observedvibekit_qa_status
    • First observedvibekit_redeploy
    • First observedvibekit_restart_app
    • First observedvibekit_run_qa
    • First observedvibekit_set_env
    • First observedvibekit_start_app
    • First observedvibekit_stop_app
    • First observedvibekit_submit_task
    • First observedvibekit_wait_for_task
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one checks database status, the other retrieves task results. No ambiguity.

Naming Consistency5/5

Both tools use the consistent 'vibekit_' prefix followed by verb_noun pattern (database_status, get_task), showing good naming uniformity.

Tool Count2/5

Only 2 tools for a server named 'VibeKit MCP' is too few, especially since a referenced tool (vibekit_submit_task) is missing, making the set feel incomplete.

Completeness2/5

The tool set is missing a critical tool (vibekit_submit_task) that is referenced in vibekit_get_task, and there are obvious gaps in domain coverage beyond database status and task retrieval.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • vibekit-mcp

    vibekit-apps
    A
    license
    B
    quality
    D
    maintenance
    Enables the management of AI-powered VibeKit apps, allowing users to control deployments, monitor logs, and perform database operations directly from MCP-compatible clients. It facilitates interaction with hosted AI agents and the execution of headless coding tasks through natural language.
    49
    10 npm
    MIT

  • dothub

    catancs
    F
    license
    Not graded
    quality
    D
    maintenance
    Publish your Claude Code setup, browse a public feed, and pull setups in. Remote MCP server + web feed in one FastAPI app.
    1
    -