vibekit_deploy — VibeKit MCP Tool
vibekit_deploy
(vibekit deploy) is one of 36 tools on the
VibeKit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vibekit_deploy from your client
- Claude Code VibeKit vibekit_deploy run in your project directory
- Claude Desktop VibeKit vibekit_deploy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VibeKit vibekit_deploy ~/.cursor/mcp.json
- VS Code VibeKit vibekit_deploy .vscode/mcp.json
- Zed VibeKit vibekit_deploy ~/.config/zed/settings.json
- Windsurf VibeKit vibekit_deploy ~/.codeium/windsurf/mcp_config.json
- Cline VibeKit vibekit_deploy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VibeKit vibekit_deploy ~/.gemini/settings.json
- Grok VibeKit vibekit_deploy .mcp.json (in your project root)
- ChatGPT VibeKit vibekit_deploy Settings → Connectors → Advanced → Developer mode
- Claude.ai VibeKit vibekit_deploy Settings → Connectors → Add custom connector
- LangChain VibeKit vibekit_deploy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vibekit-mcp https://mcp.vibekit.bot/mcp
Other tools on this server
- vibekit_list_apps
- vibekit_get_app
- vibekit_create_app
- vibekit_list_templates
- vibekit_redeploy
- vibekit_app_logs
- vibekit_restart_app
- vibekit_stop_app
- vibekit_start_app
- vibekit_app_env
- vibekit_set_env
- vibekit_delete_app
- vibekit_chat
- vibekit_agent_status
- vibekit_agent_history
- vibekit_enable_database
- vibekit_database_status
- vibekit_db_schema
- vibekit_db_query
- vibekit_db_table
- vibekit_list_deploys
- vibekit_rollback_deploy
- vibekit_run_qa
- vibekit_qa_status
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.