Dynamo MCP v2 retires executable templates

What Dynamo MCP is

Create a small, tested project from an approved template. The difference from the usual scaffolding tool is order of operations: you see the rendered files and a deterministic digest before anything is written.

What changed

Pull request #3 is the v2 security rewrite: the old Python Cookiecutter service is retired because it allowed executable templates and unrestricted output paths. A follow up, #4, cut fresh template read buffers by 99 percent without introducing stale caching.

Limits are explicit: inputs capped at 32 KiB, MCP frames at 64 KiB, templates at 256 KiB, 64 files per bundle, 100 generated projects per output root, one generation holding a root lock.

Get started

Node.js. Clone and run the CLI from your checkout:

git clone https://github.com/ruvnet/dynamo-mcp.git
cd dynamo-mcp
npm install

Start the MCP server from your host:

node /absolute/path/dynamo-mcp/src/cli.mjs mcp

Expected result: a stdio MCP server exposing six tools and a policy resource at ruv://dynamo-mcp/policy. No HTTP server is opened.

Stdio access inherits the launching operator's authority. No tool accepts a shell command, an environment map or an output directory.

Use it today

Practical case: letting an agent scaffold a service without letting it run arbitrary template code. Input is a project type — Node CLI, Node library or Python CLI; the workflow is preview, check the digest, generate; the output is a reviewed tree.

Acceptance test: preview the same template twice and compare the SHA256. Identical digests mean generation is deterministic and reviewable.

Push it further

Experimental commentary. Deterministic, fingerprinted generation is the precondition for agents creating services unattended. The limitation is template coverage: three project types is a safe start, not a platform.

Falsifiable test: edit one byte of a template bundle and try to generate. The fingerprint check must reject it.