vibekit_qa_status — VibeKit MCP Tool
vibekit_qa_status
(vibekit qa status) 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_qa_status from your client
- Claude Code VibeKit vibekit_qa_status run in your project directory
- Claude Desktop VibeKit vibekit_qa_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VibeKit vibekit_qa_status ~/.cursor/mcp.json
- VS Code VibeKit vibekit_qa_status .vscode/mcp.json
- Zed VibeKit vibekit_qa_status ~/.config/zed/settings.json
- Windsurf VibeKit vibekit_qa_status ~/.codeium/windsurf/mcp_config.json
- Cline VibeKit vibekit_qa_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VibeKit vibekit_qa_status ~/.gemini/settings.json
- Grok VibeKit vibekit_qa_status .mcp.json (in your project root)
- ChatGPT VibeKit vibekit_qa_status Settings → Connectors → Advanced → Developer mode
- Claude.ai VibeKit vibekit_qa_status Settings → Connectors → Add custom connector
- LangChain VibeKit vibekit_qa_status 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_deploy
- 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_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.