Vibe Coder MCP Server
by schwarz9987
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Optional: Node environment (e.g. production). | |
| LOG_LEVEL | No | Optional: Log level (e.g. info). | |
| GEMINI_MODEL | No | Optional: The Gemini model to use (e.g. google/gemini-2.5-flash-preview-05-20). | |
| VIBE_PROJECT_ROOT | No | Unified single variable for all project operations and root detection. Required for MCP clients. | |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key. Required to use Vibe Coder MCP. | |
| OPENROUTER_BASE_URL | No | Optional: OpenRouter base URL (default: https://openrouter.ai/api/v1). | |
| CODE_MAP_ALLOWED_DIR | No | Legacy: Security boundary for code analysis (fallback if VIBE_PROJECT_ROOT not set). | |
| VIBE_CODER_OUTPUT_DIR | No | Where generated files are saved (default: ./VibeCoderOutput/). | |
| VIBE_TASK_MANAGER_READ_DIR | No | Legacy: Security boundary for task manager operations (fallback if VIBE_PROJECT_ROOT not set). | |
| VIBE_USE_PROJECT_ROOT_AUTO_DETECTION | No | Enable automatic project root detection for CLI users (default: "true"). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessResponsive