Vibe Coder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment setting | production |
| LOG_LEVEL | No | Logging level - options include: 'fatal', 'error', 'warn', 'info', 'debug', 'trace' | info |
| GEMINI_MODEL | No | The Gemini model to use | google/gemini-pro |
| PERPLEXITY_MODEL | No | The Perplexity model to use | perplexity/sonar-small-online |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key | |
| OPENROUTER_BASE_URL | No | The base URL for OpenRouter API | https://openrouter.ai/api/v1 |
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 |
|---|---|
| researchC | Performs deep research on a given topic using Perplexity Sonar and enhances the result. |
| generate-rulesC | Creates project-specific development rules based on product description, user stories, and research. |
| generate-prdC | Creates comprehensive product requirements documents based on a product description and research. |
| generate-user-storiesC | Creates detailed user stories with acceptance criteria based on a product description and research. |
| generate-task-listC | Creates structured development task lists with dependencies based on product description, user stories, and research. |
| generate-fullstack-starter-kitA | Generates full-stack project starter kits with custom tech stacks, research-informed recommendations, and setup scripts. |
| generate-code-stubB | Generates a code stub (function, class, etc.) in a specified language based on a description. Can optionally use content from a file (relative path) as context. |
| refactor-codeC | Refactors a given code snippet based on specific instructions, optionally using surrounding file context. |
| generate-git-summaryA | Retrieves a summary of current Git changes (diff). Can show staged or unstaged changes. |
| analyze-dependenciesB | Analyzes dependency manifest files (currently supports package.json) to list project dependencies. |
| process-requestA | Processes natural language requests, determines the best tool using semantic matching and fallbacks, and either asks for confirmation or executes the tool directly. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes (e.g., generate-code-stub vs. refactor-code vs. analyze-dependencies), but there is some overlap in the generative tools (generate-prd, generate-rules, generate-task-list, generate-user-stories) which all involve creating project artifacts from similar inputs, potentially causing confusion. The process-request tool is also ambiguous as it acts as a meta-tool that could interfere with direct tool selection.
Tool names follow a consistent verb-noun pattern with hyphens (e.g., generate-code-stub, analyze-dependencies, refactor-code), which is clear and predictable. However, process-request deviates slightly by using a more generic verb and not fitting the 'generate/analyze/refactor' pattern, though it remains readable.
With 11 tools, the count is reasonable for a code and project assistance server, covering areas like code generation, refactoring, dependency analysis, and project planning. It's slightly on the higher side but well-scoped, as most tools serve distinct functions without being overwhelming.
The tool set covers key areas for coding and project development (e.g., code generation, refactoring, dependency analysis, Git summaries, and project documentation generation), but there are notable gaps such as missing code testing, deployment, or debugging tools. The research tool adds value, but the surface feels incomplete for end-to-end development workflows.