MCP Tools Overview
vibeD exposes MCP tools that an AI agent calls to deploy and manage apps. deploy_artifact runs the full flow: it classifies the source, creates a VibedApp, claims a warm sandbox, injects the source, and returns a URL.
The tool names still use "artifact" for backward compatibility, but a deploy now produces a VibedApp running on a sandbox — see App lifecycle. There is no separate "build" or "preview/promote" step anymore.
Available Tools
| Tool | Description |
|---|---|
deploy_artifact | Deploy a source tree; returns a URL once the app is Ready |
list_artifacts | List the caller's apps |
get_artifact_status | Get status, phase, and URL for one app |
update_artifact | Redeploy an app with new source |
delete_artifact | Tear an app down |
get_artifact_logs | Retrieve logs |
list_deployment_targets | Show available runtime templates |
list_versions | List version snapshots for an app |
rollback_artifact | Roll back to a previous version |
share_artifact / unshare_artifact | Grant / revoke read access |
create_share_link / list_share_links / revoke_share_link | Manage public share links |
User/department admin tools (get_user, list_users, create_department, list_departments) are also exposed when auth is enabled.
Some endpoints behind these tools are not yet fully wired (live log streaming, redeploy, rollback/versions, and snapshot-based suspend). The deploy → list → status → delete path is the supported core.
Transport
The MCP server is exposed over HTTP streamable at /mcp (the vibed server's port). For Claude Desktop, bridge to it with mcp-remote — see First deployment. stdio transport is also available via server.transport: stdio.