Skip to main content
Glama
deenesjakoruzh
VibeKit-Bot

VibeKit MCP

by VibeKit-Bot
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
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

앱의 AI 에이전트와 채팅

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에 배포하고 새 앱을 만들어줘"

  • "연락처 양식 추가에 대해 내 앱의 AI 에이전트와 채팅해줘"

  • "내 앱의 로그를 보여주고 오류가 있으면 다시 시작해줘"

  • "내 앱에 데이터베이스를 활성화하고 스키마를 보여준 다음 users 테이블을 조회해줘"

  • "내 앱의 최근 배포 내역을 나열하고 마지막으로 작동한 버전으로 롤백해줘"

  • "배포된 앱에서 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 서버가 사용자 데이터로 수행하는 작업은 구체적으로 다음과 같습니다:

  • 모든 도구 호출은 구성한 API 키로 인증되어 HTTPS를 통해 VibeKit API(https://vibekit.bot/api/v1)로 전달됩니다. 도구 입력 및 출력은 위 개인정보 처리방침에 따라 앱과 에이전트를 실행하기 위해 VibeKit에서 처리됩니다.

  • 서버 자체는 상태를 유지하지 않습니다: 디스크에 기록되는 것이 없고, 이 패키지에 의해 수집되는 분석 또는 원격 측정이 없으며, API 키는 구성(VIBEKIT_API_KEY / 확장 프로그램의 키 필드)에서 읽어 vibekit.bot에만 전송됩니다.

  • 데이터 보존, 제3자 공유 및 삭제는 위 정책에 따라 관리됩니다. 문의: 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.).

ParametersJSON Schema
NameRequiredDescriptionDefault
appIdYesApp ID (from vibekit_list_apps)

Output Schema

ParametersJSON 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 context about what status includes (provisioned, frozen) but does not contradict annotations. It is consistent but adds limited new behavioral insight.

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, front-loaded with action and resource, no wasted words. Efficient and to the point.

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 it has one parameter and an output schema, the description is sufficient for a simple read tool. It explains the purpose and kind of info returned. No major gaps.

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%, so baseline is 3. The description does not add meaning beyond the schema's parameter description ('App ID (from vibekit_list_apps)'). No additional parameter details.

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 action 'Get' and the resource 'app's database status and connection info' with examples like 'provisioned, frozen'. It distinguishes from sibling tool 'vibekit_get_task' which deals with tasks.

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?

The description implies usage for checking database status but does not provide explicit when-to-use or alternatives. No exclusions or guidance on when not to use this tool.

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID returned from vibekit_submit_task

Output Schema

ParametersJSON 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
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds that it returns status and result, providing additional behavioral context without 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, clear sentence with no unnecessary words. It is front-loaded and concise.

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?

For a simple tool with one parameter and an output schema, the description is complete enough. It explains what the tool does and the context of use.

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 description coverage is 100%, and the parameter 'taskId' is well-described in the schema. The description adds no new information about parameters beyond what is already in the schema.

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 tool retrieves status and result of a task, specifying the resource and action. It distinguishes from the sibling tool 'vibekit_database_status' by focusing on tasks.

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 usage after submitting a task via 'vibekit_submit_task', providing clear context. However, it does not explicitly state when not to use or mention alternatives beyond the sibling.

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. Dates show when Glama detected each change.

  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
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
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
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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
    39
    MIT

  • dothub

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VibeKit-Bot/vibekit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server