AUTO-GENERATED — do not edit manually

VibeServe Tools Reference

Auto-generated API documentation for all 82 MCP tools.

Tools by Category

Agenda

• agenda_activate_goal — Mark a goal as active — agents will prioritize work against this goal.
• agenda_add_goal — Add a single goal to the agenda with optional type, areas, due date and target metric.
• agenda_add_initiative — Add an initiative linked to a goal.
• agenda_complete_goal — Mark a goal as completed.
• agenda_get_active_goals — Return all active agenda goals with full metadata.
• agenda_get_impact — Get 7-day impact summary: suggestions applied per goal.
• agenda_get_status — Get current agenda: goals, progress per goal, recent entries.
• agenda_log_entry — Log a work entry (PR, refactor, test) against an agenda goal.
• agenda_set_goals — Define your business objectives, priorities, and constraints for VibeServe agents to work against.

Assessment

• vibe_benchmark — Run a benchmarking loop with ASCII graphs.
• vibe_iterate — Continuous improvement loop: critique -> repair -> verify -> repeat.
• vibe_test — Generate comprehensive test suites from source code.

Code Generation

• vibe_architect — Transform natural language intent into a detailed architecture plan with ADR decisions.
• vibe_build_pro — Full professional build: upgrade design -> architect -> code -> verify.
• vibe_code — Generate production code from an architecture plan.
• vibe_design — Generate a landing page using curated DESIGN.md templates.
• vibe_upgrade_design — Upgrade a design template with senior-dev production patterns.
• vs_generate_artifact — Generate a structured advisory artifact (not executable).

Code Review

• vibe_audit — Full system audit: backend code quality, security, performance.
• vibe_review — Multi-agent code review from three perspectives.
• vibe_verify — Validate code/specs against WCAG, design system, and code quality.
• vs_ecc_agent_shield — Run ECC AgentShield security scan on provided code content. Checks for secrets, permission risks, hook injection, MCP risks, and config issues.
• vs_plan_review — Review an execution plan and return structured critique.

Core

• editor_config — Generate editor config files (VSCode, Zed, Cursor).
• generate_ui_spec — Generate a production-ready UI specification with multi-agent critique, WCAG AAA validation, and design system enforcement
• list_design_systems — List available design systems
• validate_ui_spec — Validate a UI specification against design system and WCAG standards
• vibe_compress — Compress JSON to TOON format — 30-60% token reduction.
• vibe_health — System health stats.
• vs_ecc_health — Check ECC integration status — skills loaded, rules available.
• vs_schema_validate — Validate JSON data against a JSON schema.
• vs_validate_artifact — Validate artifact shape and size constraints.

Deployment

• vibe_deploy — Generate deployment configs for Vercel, Docker, static hosting.
• vibe_preview — Generate a preview HTML page and Playwright test script.

Documentation

• vibe_docs — Fetch documentation for a framework via Context7.

Integration

• codegraph_build — Build a knowledge graph from an indexed repo — creates call graph, import resolution, class hierarchy, and communities. Prerequisite before using other codegraph_* tools.
• codegraph_context — Get 360-degree view of a symbol — all incoming/outgoing calls, inheritance, imports, and cluster membership.
• codegraph_impact — Blast radius analysis — what depends on this symbol? Groups results by depth (WILL BREAK, LIKELY AFFECTED, MIGHT AFFECT). Use before refactoring.
• codegraph_query — Search the knowledge graph for symbols — returns callers, callees, file locations, and export status. Replaces grep for structural code questions.
• codegraph_stats — Get knowledge graph statistics — node count, edge count, clusters, edge type breakdown.
• cross_repo_suggest — Find reusable components/symbols from other repos that could help the current repo.
• find_refactors — Find refactor candidates: large files, duplicated symbols, dead code hints.
• find_test_gaps — Find source files and symbols that have no corresponding tests.
• github_issues — List GitHub issues.
• github_link_account — Link a GitHub account via personal access token. Required before repo operations.
• github_link_repo — Add a GitHub repo to VibeServe scope. Optionally clone it locally.
• github_list_repos — List repositories for the linked GitHub account.
• github_repo — Get GitHub repo info.
• github_sync_all — Sync metadata for all linked repos — pulls latest data from GitHub API.
• gitnexus_analyze — Index a repository with GitNexus — builds a knowledge graph of symbols, call chains, clusters, and execution flows. Prerequisite before using other gitnexus_* tools.
• gitnexus_context — Get a 360-degree view of a symbol — all incoming/outgoing calls, imports, processes it belongs to. Like 'go to definition' but shows the full dependency web.
• gitnexus_detect_changes — Pre-commit impact analysis — maps changed lines to affected processes. Use before committing to understand what will break.
• gitnexus_impact — Analyze blast radius — what depends on this symbol? Groups results by depth (WILL BREAK, LIKELY AFFECTED, MIGHT AFFECT). Use before refactoring.
• gitnexus_list_repos — List all repositories indexed by GitNexus (across your entire machine).
• gitnexus_query — Search the GitNexus knowledge graph — find symbols, processes, and definitions matching a query. Uses hybrid search (BM25 + semantic).
• gitnexus_status — Check GitNexus index status for the current repo — is it fresh, stale, or missing?
• gitnexus_wiki — Generate a codebase wiki from the GitNexus knowledge graph — architecture docs with mermaid diagrams.
• index_repo — Index a local repository — parses source files for symbols, components, tests, and dependencies.
• list_indexed_repos — List all repos that have been indexed.
• search_repo — Search indexed symbols across all repos, or within a specific repo.
• supabase_insert — Insert a row into a Supabase table.
• supabase_query — Query a Supabase table.
• vercel_deployments — List recent Vercel deployments.
• vs_ecc_skills_list — List available ECC skills. Optionally filter by category or harness.
• vs_opencode_execute — Execute a coding task using the OpenCode CLI agent.

Memory

• memory_stats — Get statistics on learned/stored UI specifications
• vs_memory_get — Retrieve workspace-scoped memory entries for Mutly workflows.
• vs_memory_store — Store workspace-scoped memory for Mutly workflows.

Pipeline

• check_node_env — Verify node.js environment
• detect_package_manager — Detect which package manager to use (npm, yarn, pnpm)
• generate_plan — Generate a structured task decomposition for a given objective
• ingest_learning — Save pipeline results/learnings to the local wiki
• read_file — Read content from a file in the workspace
• retrieve_context — Retrieve context from the local wiki/knowledge base
• run_biome — Run Biome linter/formatter
• run_build — Run production build
• run_install — Run package installation
• run_npm_audit — Run npm audit for dependency security
• run_playwright — Run Playwright E2E tests
• run_semgrep — Run Semgrep SAST scan on the project
• run_tsc — Run TypeScript compiler check
• write_file — Write content to a file in the workspace

---

Documentation generated from 82 tool definitions across 12 modules.