vibe-code-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBE_CODE_OFFLINE | No | 1 = לא לנסות לרשת, להשתמש רק ב‑snapshot. | 0 |
| VIBE_CODE_CACHE_TTL_MS | No | TTL ל‑cache של הרענון החי. | 43200000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| route_projectA | Given a free-text description of what you're building or the problem you need to solve (Hebrew or English), returns the best-matching tools/libraries/skills from the Vibe Code catalog (vibe-code-best-practices.vercel.app), ranked with reasons, install command and docs URL. Use this whenever the user asks 'which tool/library should I use for X'. |
| recommend_stackA | Returns a coherent end-to-end stack (one curated pick per concern: framework, styling, components, database, auth, payments, testing, deploy, etc.) from the Vibe Code catalog, biased toward an optional free-text need. Pick platform web or mobile. |
| search_toolsA | Keyword search across all 800+ catalog entries (name, category, section, description). Returns ranked matches with docs URL and install command. |
| list_domainsA | List the top-level domains (Web, Mobile, AI Agents, Skills, MCP, Design...) with section/tool counts. |
| list_sectionsA | List all sections, optionally filtered to one domain. Use to discover section ids for route_project's domain filter or get_section. |
| get_sectionA | Return every tool inside a section, by section id or name. |
| get_toolA | Return details for one tool by name (exact or partial), including its section and domain. |
| refresh_catalogA | Re-fetch the catalog from vibe-code-best-practices.vercel.app (falls back to the bundled snapshot on failure). Use if the site was recently updated. |
| catalog_statusA | Report catalog source, counts per domain, and last refresh status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | The entire catalog: domains -> sections -> tools. |
| domains | Top-level domains with counts. |
| stats | Tool/section counts. |
TDQS
Scored across 9 tools
Most tools are distinct, but recommend_stack and route_project both provide recommendations based on a description, causing potential overlap. Descriptions help differentiate, but an agent may still be uncertain which to use for a given query.
Most tools follow a verb_noun pattern (get_, list_, recommend_, refresh_, route_, search_), but catalog_status is a noun_noun phrase, breaking the convention. Overall, naming is largely consistent and intuitive.
With 9 tools covering browsing, search, recommendation, status, and refresh, the count is well-scoped for a catalog server. Each tool has a clear role, and the number feels appropriate without being overwhelming or insufficient.
The server provides comprehensive browsing (by domain, section, tool), searching, recommendation, and status. Missing a direct 'list all tools' endpoint, but the combination of search and section browsing covers most discovery needs. Minor gap for read-only catalog.