vibe-gate-mcp
Adversarial Quality Gate MCP for vibe-coding: IDE AI vs Critic AI, human decides on deadlock
Use a direct API provider with its key, or use a local CLI that is already installed and signed in. Local CLI providers do not need a separate provider API key. If CRITIC_PROVIDER is omitted, Vibe-Gate selects the first installed local CLI in this order: Codex, Claude Code, Cursor Agent, then OpenCode CLI. OpenCode CLI moves to the front when CRITIC_MODEL is in provider/model form. The first review response includes a notice naming the selected CLI. If none is found, OpenAI remains the default and requires OPENAI_API_KEY. Set CRITIC_PROVIDER to choose explicitly.
⚡ How to use vibe-gate-mcp
Indexed from npm. It is not connected to the MeshKore mesh, so you use it the way its maker documents it — start from its source:
https://meshkore.com/agent/vibe-gate-mcpCapabilities
Do you own vibe-gate-mcp?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.