Server providing Argo CD integration for MCP clients.
Nothing to run from here
Vibekit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
3
downloads a day
remote
at its publisher
117
downloads in 30d
What it does
MCP server for VibeKit — deploy apps, manage hosting, chat with AI agents, and run coding tasks from Claude Desktop, Cursor, and other MCP clients.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vibekit-mcp https://mcp.vibekit.bot/mcp
# 2 — ask your agent for something these tools do
# vibekit_list_apps, vibekit_get_app, vibekit_create_app and 33 more
Vibekit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VBAll 1 server
vibekit-bot1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http vibekit-mcp https://mcp.vibekit.bot/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
36 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config. Use the appId from vibekit_list_apps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| template | string | yes | Template id from vibekit_list_templates (e.g. 'landing', 'dashboard', 'blog', 'saas', 'crud-api') |
| subdomain | string | yes | Desired subdomain — the app goes live at <subdomain>.vibekit.bot. Lowercase letters, numbers, and hyphens. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | yes | GitHub repo as 'owner/repo' (e.g. 'your-username/my-app') |
| subdomain | string | yes | Desired subdomain — the app goes live at <subdomain>.vibekit.bot. Lowercase letters, numbers, and hyphens. |
Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| lines | number | no | Number of log lines to retrieve (default 100) |
Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| vars | object | yes | Key-value pairs to set as environment variables, e.g. { "API_KEY": "...", "NODE_ENV": "production" } |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
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 activit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| message | string | yes | What you want the agent to do or change — be specific about features, design, and behavior. |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Get the recent chat history between the user and an app's AI agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| limit | number | no | Maximum number of messages to return (default 20) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Get an app's database status and connection info (whether it's provisioned, frozen, etc.).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| sql | string | yes | SQL to execute (max 5000 chars). Reads and writes both allowed. |
Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| table | string | yes | Table name (see vibekit_db_schema) |
| limit | number | no | Max rows to return (default 50, max 200) |
| offset | number | no | Row offset for pagination (default 0) |
List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| limit | number | no | Max deploys to return (default 20, max 50) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
| deployId | string | yes | Deploy ID to roll back to (from vibekit_list_deploys) |
Kick off an automated QA run (headless-browser checks) against a hosted app. Poll vibekit_qa_status for results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
Get the latest automated QA results and status for an app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | App ID (from vibekit_list_apps) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | What you want built or changed. Be specific about features, design, and behavior. |
| repo | string | no | GitHub repo as 'owner/repo'. Optional — uses the user's current repo if omitted. |
| branch | string | no | Git branch to work on (default 'main') |
| deploy | boolean | no | Auto-deploy to <subdomain>.vibekit.bot when done (default true) |
| callbackUrl | string | no | Optional webhook URL to receive a task-completion notification. |
Get the status and result of a task submitted via vibekit_submit_task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskId | string | yes | Task ID returned from vibekit_submit_task |
List recent coding tasks, optionally filtered by status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Max number of tasks to return (default 10) |
| status | string | no | Filter by task status |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskId | string | yes | Task ID to wait for (from vibekit_submit_task) |
| timeoutSeconds | number | no | Max seconds to wait (default 300; the remote connector caps this at 120) |
Cancel a running task by taskId. No-op if it has already finished.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskId | string | yes | Task ID to cancel (from vibekit_submit_task) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | What to do on each run, e.g. 'Improve SEO and page speed' |
| repo | string | yes | GitHub repo as 'owner/repo' |
| cron | string | yes | Cron expression, e.g. '0 9 * * 1' for every Monday at 9am UTC |
| name | string | no | Friendly name for the schedule (optional) |
List all of the account's scheduled recurring tasks.
No parameter schema on file.
Delete a scheduled recurring task by scheduleId. Confirm with the user first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | Schedule ID to delete (from vibekit_list_schedules) |
Get VibeKit account info: plan, credit balance, and usage.
No parameter schema on file.
List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | no | Filter skills by tag (e.g. 'react', 'database', 'security') |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Skill ID from vibekit_list_skills (e.g. 'nextjs', 'trpc', 'auth') |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Vibekit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.8.0 · scanned 6 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest11a59cb23c000f072e20285af339e4021593e92e8c79aff266d083e969d08e26
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest11a59cb23c000f07
Scanned2026-10-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.8.0.
0.8.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Vibekit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.