vyges mcp

Generated from vyges-mcp --help. Do not edit by hand — run scripts/gen-cli-reference.sh.

vyges-mcp — local stdio MCP server exposing the installed Vyges Loom engines

usage:
  vyges mcp                 start the stdio MCP server (an MCP client spawns this)
  vyges mcp tools           show how each engine + external tool resolves on this host
  vyges mcp tools --init    write a starter ~/.vyges/tools.json (with $schema) to pin from
  vyges mcp feedback <gds> --rules <deck> [--top C] [--golden G] [-o SVG]
                            agentic feedback bundle: render + DRC verdicts + score
  vyges mcp emap <netlist> --top T --lib L.lib [--lib …] --lef X.lef [--lef …]
                 [--sdc S] [-o out.v] [--no-multioutput] [--scene fast]
                            multi-output techmap (OpenROAD resynth_emap): before/after/delta
  vyges mcp setup [--dry-run] [--uninstall]
                            detect installed AI IDEs (Claude Code / Cursor / VS Code)
                            and register `vyges mcp` with each (user scope)
  vyges mcp install [dir]   register `vyges mcp` in <dir>/.mcp.json (project scope)
  vyges mcp uninstall [dir]  remove it from <dir>/.mcp.json
  vyges mcp --list          print the tools this server would advertise, then exit
  vyges mcp --version       print the version
  vyges mcp --help          show this help

No port, no auth: the server talks JSON-RPC over stdin/stdout and exposes your
own installed `vyges-<engine>` binaries to your own local agent. Install engines
with `vyges install loom`, then `vyges mcp setup` (all your AI IDEs) or
`vyges mcp install` (just this project).