Use with AI agents

vibe-mcp is a local MCP server that comes with the CLI. It uses the token from vibe login, so log in first (Quick start). Then add it to your tool:

claude mcp add vibedeploy --scope user -- vibe-mcp
claude mcp list

Restart running sessions to load it.

Desktop apps often don’t see your shell’s PATH, so use absolute paths. Get them with:

which node; echo "$(npm root -g)/vibedeploy/bin/vibe-mcp.mjs"

Then Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "vibedeploy": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/node_modules/vibedeploy/bin/vibe-mcp.mjs"]
    }
  }
}

Quit Claude completely (⌘Q) and start it again.

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{ "mcpServers": { "vibedeploy": { "command": "vibe-mcp" } } }

Enable vibedeploy under Cursor Settings → MCP. If it does not start, use the absolute paths from the Claude Desktop tab.

codex mcp add vibedeploy -- vibe-mcp

or in ~/.codex/config.toml:

[mcp_servers.vibedeploy]
command = "vibe-mcp"
tool_timeout_sec = 600   # a first build can take a few minutes

Check with /mcp in a new session.

Any MCP client that starts a local stdio server works. The command is vibe-mcp, with no arguments. Instead of vibe login you can set VIBE_TOKEN in the client’s environment.

Ask for a deploy

In a project folder, ask your agent:

Deploy this folder with vibedeploy.

The agent calls deploy_app, which blocks until the app is live or the deploy failed. On failure it returns the error, a hint and the relevant build or container logs, so the agent can fix the code and deploy again by itself. A typical first failure is a server listening on localhost:3000; the hint tells the agent to use 0.0.0.0 and $PORT.

More things to ask:

“This app needs a Postgres database.” The agent creates one and links it: the app gets DATABASE_URL. See Databases.
“Why is shop not working?” The agent reads app_status (crash reason, memory use, warnings) and app_logs.
“Set the Stripe key for shop.” set_env stores it as a secret; values are never shown again.

All tools: MCP tools.