vibe-gate-mcp

What this does

vibe-gate-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

VIBE_WORKSPACE_ROOT
CRITIC_PROVIDER
CRITIC_MODEL
CRITIC_PERSONA
OPENAI_API_KEY
ANTHROPIC_API_KEY
GOOGLE_GENERATIVE_AI_API_KEY
MINIMAX_API_KEY
OPENCODE_API_KEY
OPENCODE_PLAN
CODEX_CLI_PATH
CLAUDE_CODE_CLI_PATH
CURSOR_AGENT_CLI_PATH
OPENCODE_CLI_PATH
CRITIC_CLI_TIMEOUT_MS
DEBUG

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install vibe-gate-mcp?

Run the Claude Code command in the install section to add vibe-gate-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with vibe-gate-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to vibe-gate-mcp as well.

Does vibe-gate-mcp need an API key?

Yes. Before it can run, set these environment variables: VIBE_WORKSPACE_ROOT, CRITIC_PROVIDER, CRITIC_MODEL, CRITIC_PERSONA, OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_GENERATIVE_AI_API_KEY, MINIMAX_API_KEY, OPENCODE_API_KEY, OPENCODE_PLAN, CODEX_CLI_PATH, CLAUDE_CODE_CLI_PATH, CURSOR_AGENT_CLI_PATH, OPENCODE_CLI_PATH, CRITIC_CLI_TIMEOUT_MS, DEBUG. They go in the env block of your MCP config.