// the take
A toolkit (CLI, VS Code/Cursor extension, and an agent-skills/MCP layer) that turns n8n workflow management into a git-friendly, agent-operable workflow: pull workflows into TypeScript files, edit and validate them locally, push them back, and promote between environments. Aimed at teams running n8n who want workflows in version control and at anyone building AI agents that need to safely construct or edit n8n workflows.
The TypeScript workflow representation (decorators for nodes/links) is the actual useful idea here — n8n's native JSON export is a diff nightmare in a PR, and a typed, readable source format fixes that. The skills/MCP layer shipping full schemas for 537 nodes directly addresses a real failure mode: agents hallucinating node parameters when generating n8n JSON blind. Sync is explicit (pull/push/resolve), not auto-magic, which avoids the classic GitOps footgun of silently overwriting whatever's live in the n8n instance. There's a real CI pipeline and a sizeable test suite (unit + integration across cli, mcp, skills, transformer packages), which is more rigor than most tools in this space bother with.
Surface area is large for what's effectively a single-maintainer project (CLI + extension + MCP server + skills package + transformer + a separate n8n-manager + an OpenClaw plugin) — that's a lot of surfaces to keep mutually in sync as n8n's own schema changes. It's explicitly coupled to n8n's internal node schema rather than a stable public API; the README itself warns to keep n8n updated for 'best generation and validation results,' which means schema drift between releases is a known, user-facing risk, not a hypothetical. The TypeScript DSL is a bespoke abstraction over n8n's real JSON format, so any gap between what the transformer encodes and what n8n actually expects (new parameter gating, new node types) shows up as a push/validate failure rather than a compile error — the existence of a dedicated 'preflight-node-validator' and 'schema-overlay-manager' suggests this gap is already a recurring source of bugs. `promote` remaps credentials and workflow references across environments and pushes by default; get that remap logic wrong and you silently ship a broken workflow to the target environment, with `--dry-run` as the only safety net.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →