Skip to main content
Glama
Sign In
deenesjakoruzh
VibeKit MCP

VibeKit MCP

by VibeKit-Bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibekit-mcp

Servidor MCP para VibeKit: despliega aplicaciones, gestiona el hosting y chatea con agentes de IA desde cualquier cliente MCP.

Este paquete es para acceso a la nube/API de VibeKit. No conecta tu instancia local de Claude Code a Telegram. Para el control remoto de tu máquina local, usa vibekit-agent.

Úsalo de forma remota (sin instalación)

VibeKit también funciona como servidor remoto alojado, por lo que los clientes que aceptan una URL MCP remota (conectores web de claude.ai, ChatGPT, etc.) no necesitan instalación.

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

Pega esa URL en el campo de "conector personalizado" / "servidor MCP remoto" de tu cliente. Los clientes que permiten configurar cabeceras pueden enviar Authorization: Bearer vk_your_api_key_here y usar la URL base https://mcp.vibekit.bot/mcp. Consulta Obtener una clave de API a continuación.

¿Prefieres una instalación local stdio (p. ej. Claude Desktop)? Usa los pasos siguientes.

Related MCP server: vibekit-mcp

Obtener una clave de API

Las claves empiezan con vk_. Hay dos formas de obtener una:

  • Instantánea, sin registro: una sola solicitud devuelve una clave.

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

Guarda la clave devuelta y reutilízala. Cada llamada a /auth/register crea una cuenta completamente nueva, así que llámala una vez, no por solicitud.

  • Desde tu cuenta: si ya usas VibeKit, copia o regenera tu clave en el panel web o en los ajustes de la app de iOS.

Instalación

npm install -g vibekit-mcp

Configuración

  1. Obtén una clave de API de VibeKit (consulta Obtener una clave de API más arriba).

  2. Añádela a la configuración de tu cliente MCP (p. ej. Claude Desktop) (~/Library/Application Support/Claude/claude_desktop_config.json en macOS):

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

  1. Reinicia tu cliente MCP

Herramientas disponibles

Hosting

Herramienta

Descripción

vibekit_list_apps

Listar todas las aplicaciones alojadas

vibekit_get_app

Obtener detalles de una aplicación específica

vibekit_list_templates

Listar plantillas de inicio para vibekit_create_app

vibekit_create_app

Crear una nueva aplicación a partir de una plantilla

vibekit_deploy

Desplegar un repositorio de GitHub en el hosting

vibekit_redeploy

Redesplegar la aplicación con el código más reciente

vibekit_list_deploys

Listar los despliegues recientes de una aplicación con estado y commit

vibekit_rollback_deploy

Revertir una aplicación a un despliegue anterior

vibekit_app_logs

Obtener registros de la aplicación

vibekit_restart_app

Reiniciar una aplicación

vibekit_stop_app

Detener una aplicación

vibekit_start_app

Iniciar una aplicación detenida

vibekit_app_env

Obtener variables de entorno de la aplicación

vibekit_set_env

Establecer variables de entorno de la aplicación

vibekit_delete_app

Eliminar una aplicación permanentemente

Agente

Herramienta

Descripción

vibekit_chat

Chatear con el agente de IA de una aplicación

vibekit_agent_status

Obtener el estado del agente

vibekit_agent_history

Obtener el historial de chat con el agente

Base de datos

Herramienta

Descripción

vibekit_enable_database

Habilitar una base de datos Postgres para una aplicación

vibekit_database_status

Obtener el estado de la base de datos e información de conexión

vibekit_db_schema

Obtener el esquema de la base de datos (cada tabla y sus columnas)

vibekit_db_query

Ejecutar una consulta SQL de solo lectura (solo SELECT, hasta 200 filas)

vibekit_db_table

Explorar las filas de una tabla con paginación y ordenamiento

QA

Herramienta

Descripción

vibekit_run_qa

Ejecutar pruebas de QA automatizadas

vibekit_qa_status

Obtener resultados de pruebas de QA

Tareas

Herramienta

Descripción

vibekit_submit_task

Enviar una tarea de codificación

vibekit_get_task

Obtener estado/resultado de la tarea

vibekit_list_tasks

Listar tareas recientes

vibekit_wait_for_task

Esperar a que se complete la tarea

vibekit_cancel_task

Cancelar una tarea en ejecución

vibekit_create_schedule

Crear una tarea programada recurrente

vibekit_list_schedules

Listar tareas programadas

vibekit_delete_schedule

Eliminar tarea programada

Cuenta

Herramienta

Descripción

vibekit_account

Obtener información de la cuenta (plan, créditos, uso)

vibekit_list_skills

Listar habilidades de implementación

vibekit_get_skill

Obtener contenido de una habilidad específica

Ejemplo de uso

Una vez configurado, puedes usar indicaciones como:

  • "Desplegar mi repositorio de GitHub en VibeKit y crear una nueva aplicación"

  • "Chatear con el agente de IA de mi aplicación sobre cómo añadir un formulario de contacto"

  • "Mostrarme los registros de mi aplicación y reiniciarla si hay errores"

  • "Habilitar una base de datos para mi aplicación, luego mostrarme su esquema y consultar la tabla de usuarios"

  • "Listar los despliegues recientes de mi aplicación y revertir al último que funcionaba"

  • "Ejecutar pruebas de QA en mi aplicación desplegada"

  • "Comprobar el saldo de mi cuenta de VibeKit y listar mis aplicaciones"

  • "Crear una programación semanal para mejorar el rendimiento de mi aplicación"

Variables de entorno

Variable

Descripción

Default

VIBEKIT_API_KEY

Tu clave de API de VibeKit (obligatoria)

ninguna

VIBEKIT_API_URL

URL base de la API

https://vibekit.bot/api/v1

Paquetes relacionados

  • vibekit-cli: cliente de terminal para flujos de trabajo en la nube de VibeKit

  • vibekit-agent: puente de Telegram para Claude Code local en tu propia máquina

Enlaces

Política de privacidad

Política de privacidad de VibeKit: https://vibekit.bot/privacy

Lo que este servidor MCP hace con tus datos, concretamente:

  • Cada llamada a una herramienta se reenvía a la API de VibeKit (https://vibekit.bot/api/v1) a través de HTTPS, autenticada con la clave de API que configures. Las entradas y salidas de las herramientas son procesadas por VibeKit para ejecutar tus aplicaciones y agentes, según la política de privacidad anterior.

  • El servidor en sí no guarda estado: no se escribe nada en el disco, este paquete no recopila análisis ni telemetría, y tu clave de API se lee de la configuración (VIBEKIT_API_KEY / el campo de clave de la extensión) y se envía solo a vibekit.bot.

  • La retención de datos, el intercambio con terceros y la eliminación se rigen por la política anterior. Preguntas: 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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.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
    -