# VibeKit (remote · mcp.vibekit.bot)

Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.vibekit.bot`: 70/100 (this document), [markdown](https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp.md), [page](https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.vibekit.bot/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (vibekit_delete_app).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 3044 tokens (~84/item across 36 items; 36 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http vibekit-bot-vibekit-mcp https://mcp.vibekit.bot/mcp
```

### Codex

```toml
[mcp_servers.vibekit-bot-vibekit-mcp]
url = "https://mcp.vibekit.bot/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vibekit-bot-vibekit-mcp": {
      "type": "remote",
      "url": "https://mcp.vibekit.bot/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vibekit-bot-vibekit-mcp --url https://mcp.vibekit.bot/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vibekit-bot-vibekit-mcp:
    url: "https://mcp.vibekit.bot/mcp"
```

### Other

```json
{
  "mcpServers": {
    "vibekit-bot-vibekit-mcp": {
      "type": "http",
      "url": "https://mcp.vibekit.bot/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (36)

### `vibekit_list_apps` (~49 tokens)

VibeKit List Apps

List all hosted apps in your VibeKit account, each with its id, subdomain, status, and live URL. Start here to get an appId for the other app tools.

Output parameters:

- `data`: Array of hosted apps, each with id, subdomain, status, and live URL.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_get_app` (~63 tokens)

VibeKit Get App

Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: App details: subdomain, status, live URL, container stats, and infrastructure topology.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_create_app` (~138 tokens)

VibeKit Create App

Create a new hosted app from a starter template and deploy it live at <subdomain>.vibekit.bot. Call vibekit_list_templates first to pick a valid template. To deploy existing code from a GitHub repo instead, use vibekit_deploy.

Input parameters:

- `subdomain` (string, required): Desired subdomain — the app goes live at <subdomain>.vibekit.bot. Lowercase letters, numbers, and hyphens.
- `template` (string, required): Template id from vibekit_list_templates (e.g. 'landing', 'dashboard', 'blog', 'saas', 'crud-api')

Output parameters:

- `data`: The created app: appId, subdomain, live URL, and initial deploy status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_list_templates` (~52 tokens)

VibeKit List Templates

List the starter templates available to vibekit_create_app (e.g. landing, dashboard, blog, saas, crud-api). Call this before vibekit_create_app to choose a valid template.

Output parameters:

- `data`: Array of starter templates with name and description.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_deploy` (~131 tokens)

VibeKit Deploy

Deploy a GitHub repo to VibeKit hosting, live at <subdomain>.vibekit.bot (Fargate container behind nginx, SSL automatic). Use when the code already lives in a GitHub repo; for a starter template instead use vibekit_create_app.

Input parameters:

- `repo` (string, required): GitHub repo as 'owner/repo' (e.g. 'your-username/my-app')
- `subdomain` (string, required): Desired subdomain — the app goes live at <subdomain>.vibekit.bot. Lowercase letters, numbers, and hyphens.

Output parameters:

- `data`: Deploy result: deployUrl (https://<subdomain>.vibekit.bot) and appId.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_redeploy` (~53 tokens)

VibeKit Redeploy

Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Redeploy confirmation with deploy/task status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_app_logs` (~69 tokens)

VibeKit App Logs

Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `lines` (number): Number of log lines to retrieve (default 100)

Output parameters:

- `data`: Recent container log lines for the app.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_restart_app` (~50 tokens)

VibeKit Restart App

Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Restart confirmation and resulting container status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_stop_app` (~63 tokens)

VibeKit Stop App

Stop a hosted app's container. The app stays in your account and can be brought back with vibekit_start_app. Use to take an app offline without deleting it.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Stop confirmation; the app is retained but the container is freed.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_start_app` (~51 tokens)

VibeKit Start App

Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Start confirmation and resulting container status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_app_env` (~54 tokens)

VibeKit Get Env Vars

Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: The app's environment variables as key-value pairs.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_set_env` (~89 tokens)

VibeKit Set Env Vars

Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `vars` (object, required): Key-value pairs to set as environment variables, e.g. { "API_KEY": "...", "NODE_ENV": "production" }

Output parameters:

- `data`: Confirmation of the updated environment variables.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_delete_app` (~71 tokens)

VibeKit Delete App

Permanently delete a hosted app — stops the container and removes its workspace, database, env vars, and subdomain. Irreversible (the GitHub repo is NOT touched). Confirm with the user before calling.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Deletion confirmation for the app, its container, and its agent.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_chat` (~171 tokens)

VibeKit Chat with Agent

Send a message to an app's built-in AI coding agent, which reads, writes, and modifies the app's code and redeploys it. Use for 'build/make a change to my app' requests. If the agent finishes quickly you get its reply directly. Otherwise you get status:'working' — do NOT resend; instead give the user LIVE progress: poll vibekit_agent_status every few seconds and relay the current step from activity.status ('editing the homepage…', 'deploying…') until activity.done, then read vibekit_agent_history for the final reply.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `message` (string, required): What you want the agent to do or change — be specific about features, design, and behavior.

Output parameters:

- `data`: The agent's reply and remaining credit balance, or a status:'working' note with polling instructions when the coding turn is still running.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_agent_status` (~164 tokens)

VibeKit Agent Status

Check whether an app's AI agent is idle or working, and get its LIVE progress. Returns activity.status = the current human-readable build step (e.g. 'editing index.html', 'deploying'), activity.steps = the steps so far, and activity.done = whether the turn finished. Poll this every few seconds while a build is running and relay activity.status to the user so they see progress. Once activity.done is true the response also includes liveCheck = a server-side fetch of the deployed page ({ url, ok, httpStatus, title }); use it to confirm the app is live and renders — do NOT curl/fetch the URL yourself, your sandbox may block it.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Agent status: idle/working, current model, context usage, and app info.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_agent_history` (~60 tokens)

VibeKit Agent History

Get the recent chat history between the user and an app's AI agent.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `limit` (number): Maximum number of messages to return (default 20)

Output parameters:

- `data`: Array of recent chat messages between the user and the app's agent.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_enable_database` (~71 tokens)

VibeKit Enable Database

Provision a Postgres database for an app (idempotent — safe if already enabled). Required before the vibekit_db_* tools work. Note: free-tier apps need the $3/mo Database add-on.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Database provisioning result including the assigned schema name; DATABASE_URL is injected on next deploy.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_database_status` (~47 tokens)

VibeKit Database Status

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

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Database stats: tables, storage, and connection info.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_db_schema` (~55 tokens)

VibeKit Database Schema

Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Full database schema: tables, columns, and types.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_db_query` (~138 tokens)

VibeKit Run SQL Query

Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `sql` (string, required): SQL to execute (max 5000 chars). Reads and writes both allowed.

Output parameters:

- `data`: Query result rows.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_db_table` (~100 tokens)

VibeKit Browse Table

Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `limit` (number): Max rows to return (default 50, max 200)
- `offset` (number): Row offset for pagination (default 0)
- `table` (string, required): Table name (see vibekit_db_schema)

Output parameters:

- `data`: Rows from the requested table with pagination applied.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_list_deploys` (~83 tokens)

VibeKit List Deploys

List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `limit` (number): Max deploys to return (default 20, max 50)

Output parameters:

- `data`: Array of past deploys with timestamps and commit info.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_rollback_deploy` (~91 tokens)

VibeKit Rollback Deploy

Roll an app back to a previous deploy (get the deployId from vibekit_list_deploys). The container restarts on the rolled-back build; reversible by rolling forward again.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)
- `deployId` (string, required): Deploy ID to roll back to (from vibekit_list_deploys)

Output parameters:

- `data`: Rollback confirmation for the selected deploy snapshot.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_run_qa` (~56 tokens)

VibeKit Run QA

Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: QA run start confirmation with run id/status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_qa_status` (~41 tokens)

VibeKit QA Status

Get the latest automated QA results and status for an app.

Input parameters:

- `appId` (string, required): App ID (from vibekit_list_apps)

Output parameters:

- `data`: Latest QA run status and results summary.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_submit_task` (~190 tokens)

VibeKit Submit Task

Submit an autonomous coding task. The AI writes the code, commits to GitHub, and (by default) deploys to <subdomain>.vibekit.bot. Returns a taskId — poll vibekit_get_task or block with vibekit_wait_for_task. Use for 'build X' or 'change X' work against a repo.

Input parameters:

- `branch` (string): Git branch to work on (default 'main')
- `callbackUrl` (string): Optional webhook URL to receive a task-completion notification.
- `deploy` (boolean): Auto-deploy to <subdomain>.vibekit.bot when done (default true)
- `repo` (string): GitHub repo as 'owner/repo'. Optional — uses the user's current repo if omitted.
- `task` (string, required): What you want built or changed. Be specific about features, design, and behavior.

Output parameters:

- `data`: The created task: taskId and initial status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_get_task` (~44 tokens)

VibeKit Get Task

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

Input parameters:

- `taskId` (string, required): Task ID returned from vibekit_submit_task

Output parameters:

- `data`: Task details: status, logs/result summary, and repo info.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_list_tasks` (~49 tokens)

VibeKit List Tasks

List recent coding tasks, optionally filtered by status.

Input parameters:

- `limit` (number): Max number of tasks to return (default 10)
- `status` (string): Filter by task status

Output parameters:

- `data`: Array of tasks with id and status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_wait_for_task` (~95 tokens)

VibeKit Wait for Task

Block until a submitted task finishes (or the timeout), polling every 5 seconds, then return its result. Use right after vibekit_submit_task when you want the final result inline.

Input parameters:

- `taskId` (string, required): Task ID to wait for (from vibekit_submit_task)
- `timeoutSeconds` (number): Max seconds to wait (default 300; the remote connector caps this at 120)

Output parameters:

- `data`: Final task state after polling: completed or failed, with result details.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_cancel_task` (~46 tokens)

VibeKit Cancel Task

Cancel a running task by taskId. No-op if it has already finished.

Input parameters:

- `taskId` (string, required): Task ID to cancel (from vibekit_submit_task)

Output parameters:

- `data`: Cancellation confirmation for the task.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_create_schedule` (~130 tokens)

VibeKit Create Schedule

Create a recurring coding task that the AI runs automatically on a cron schedule (e.g. a weekly SEO pass). Use for 'every Monday, do X to my repo' requests.

Input parameters:

- `cron` (string, required): Cron expression, e.g. '0 9 * * 1' for every Monday at 9am UTC
- `name` (string): Friendly name for the schedule (optional)
- `repo` (string, required): GitHub repo as 'owner/repo'
- `task` (string, required): What to do on each run, e.g. 'Improve SEO and page speed'

Output parameters:

- `data`: The created schedule: id, name, and cron expression.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_list_schedules` (~22 tokens)

VibeKit List Schedules

List all of the account's scheduled recurring tasks.

Output parameters:

- `data`: Array of scheduled tasks with id, name, and cron expression.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_delete_schedule` (~46 tokens)

VibeKit Delete Schedule

Delete a scheduled recurring task by scheduleId. Confirm with the user first.

Input parameters:

- `scheduleId` (string, required): Schedule ID to delete (from vibekit_list_schedules)

Output parameters:

- `data`: Deletion confirmation for the schedule.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_account` (~25 tokens)

VibeKit Account Info

Get VibeKit account info: plan, credit balance, and usage.

Output parameters:

- `data`: Account info: plan, credits, usage, and API key status.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_list_skills` (~69 tokens)

VibeKit List Skills

List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill.

Input parameters:

- `tag` (string): Filter skills by tag (e.g. 'react', 'database', 'security')

Output parameters:

- `data`: Array of available skills, optionally filtered by tag, each with id, name, and tags.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

### `vibekit_get_skill` (~75 tokens)

VibeKit Get Skill

Fetch the full content of a specific skill — implementation patterns, code examples, and best practices for a domain. Fetch on-demand when you need guidance on a specific topic.

Input parameters:

- `id` (string, required): Skill ID from vibekit_list_skills (e.g. 'nextjs', 'trpc', 'auth')

Output parameters:

- `data`: The skill's id and full SKILL.md content.
- `error` (string): Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).
- `ok` (boolean): Whether the call succeeded.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://mcp.vibekit.bot/mcp
- Repository: https://github.com/VibeKit-Bot/vibekit-mcp
- Website: https://vibekit.bot/
- Changelog RSS feed: https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vibekit-bot-vibekit-mcp/mcp