The awkward part of Yeoman is discovering which generator to use and what arguments it expects. Search and option discovery are separate tools here, so the run itself starts with the right arguments instead of a failed first attempt.
An MCP server for Yeoman generators. It searches npm for templates, reports the options and arguments a generator expects, then runs it in a working directory you name with the app name, version, options and positional arguments you supply.
- Yeoman templates searched on npm by comma-separated keywords, with a page size you set (yeoman_search_templates)
- A generator's required options and arguments read before it is run (yeoman_get_generator_options)
- A generator run in a working directory you name, with app name, version, options object and extra positional arguments (yeoman_generate)
- Generator names given without the generator- prefix
Node.js v16 or later with npm or yarn; run it through npx or from a built clone, or install it in one command through Smithery. The generator writes into the working directory you pass, so point it at the directory you actually want scaffolded.
One command — npx @smithery/cli@latest install mcp-yeoman --client claude