Dynamo MCP
Allows discovery, registration, and management of cookiecutter templates, and generation of projects from those templates.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dynamo MCP list all available templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dynamo MCP v2
Create a small, tested software project from an approved template. Dynamo shows the exact files first, verifies the template fingerprint, then writes a new project without running template scripts or downloading code.
This is a security focused alpha release. The old Python Cookiecutter service is retired because it allowed executable templates and unrestricted output paths. Its historical documentation remains in the migration archive.
Capabilities
Capability | Available behavior |
Project types | Node CLI, Node library, Python CLI |
Preview | Complete rendered files and deterministic SHA256 digest |
Template integrity | Bundled JSON templates pinned by digest in a reviewed manifest |
Generation | Private operator directory, exclusive reservation, staged atomic source publication |
Security | No hooks, no remote downloads, no arbitrary paths, no overwrite, file and project quotas |
Agent tools | Official MCP SDK 2 stdio server, six tools, policy resource |
Evaluation | Generated project tests, hostile fixtures, SDK integration tests, local benchmark |
MetaHarness | Maintainer/security/release/benchmark profiles, sessions, field memory adapter, host configs |
Autogenous | Actual upstream fitness gates, automatic promotion disabled |
Related MCP server: agentic-patterns
Install and try
Requires Node 22 or 24, npm, and Python 3.11+ for Python template tests. Linux is the validated generation platform.
git clone https://github.com/ruvnet/dynamo-mcp.git
cd dynamo-mcp
npm ci --ignore-scripts
npm test
node src/cli.mjs list
node src/cli.mjs preview '{"template":"node-cli","name":"my-project"}'Create an operator owned output directory with private permissions. Existing project names are never overwritten.
mkdir -m 700 "$HOME/dynamo-projects"
export DYNAMO_OUTPUT_ROOT="$HOME/dynamo-projects"
export DYNAMO_ALLOW_GENERATE=1
node src/cli.mjs generate '{"template":"node-cli","name":"my-project"}'
cd "$DYNAMO_OUTPUT_ROOT/my-project/source"
npm test
npm startA generated harness.json declares validation and ecosystem links; it is not an installed full MetaHarness. The full working MetaHarness belongs to this repository and is installed separately using the linked guide.
MCP and CLI
Start node /absolute/path/dynamo-mcp/src/cli.mjs mcp from your MCP host. Stdio access inherits the launching operator's authority. No HTTP server is exposed. Generation additionally requires both environment variables above. Validation requires DYNAMO_ALLOW_VALIDATION=1; no tool accepts a shell command, environment map, or output directory.
CLI command | MCP tool |
|
|
|
|
|
|
|
|
|
|
|
|
Resource: ruv://dynamo-mcp/policy. CLI test is explicit local authorization to run the fixed core suite. npm test runs the complete suite, including the MCP client. MCP validation runs the core suite without recursive MCP invocation. Benchmarks measure local template verification and rendering only.
Operations and limits
Inputs are capped at 32 KiB, MCP frames at 64 KiB, templates at 256 KiB, files at 64 KiB and 64 per bundle, generated projects at 100 per output root. One generation holds a root lock; two tool calls may be active. Validation is one fixed subprocess with a 30 second deadline and 64 KiB output cap; environment secrets are not forwarded.
A crash leaves a lock and potentially a private staging directory. Stop all Dynamo instances, inspect the incomplete project, and remove the stale lock and incomplete reservation manually before retrying. Dynamo never guesses that a lock is stale. Atomic visibility of the source directory does not guarantee power loss durability. Protect the root and its parents from other writers; this is not isolation from another process running under your own account. Hash receipts prove content consistency, not trusted authorship.
Development and delivery
npm test
npm run benchmark
npm auditCI runs Node 22 and 24, all project and SDK tests, audit, and benchmark artifact upload. Tagged releases create a source archive as a CI artifact; no registry or live deployment occurs automatically. ADR, security review, and validation evidence document scope and limitations.
RuV ecosystem
RuFlo coordinates work. MetaHarness evaluates changes. Autogenous supplies fitness gates. Guardrail evaluates policy. Federated MCP provides bounded federation reads. x.ruv.io MCP is a separate federation service; Dynamo does not publish federation messages or acquire credentials.
Available Tools
6 toolsproject_benchmarkCRead-only
project benchmark
Inputs: no named parameters.
project_generateA
Generate bundled inert project under operator private root; local opt-in required.
Inputs: name (required), template (required).
project_statusCRead-only
project status
Inputs: no named parameters.
project_validateDRead-only
project validate
Inputs: no named parameters.
template_previewDRead-only
template preview
Inputs: name (required), template (required).
templates_listCRead-only
templates list
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct resource-action pair: templates list/preview are separate from project generate/status/validate/benchmark. No two tools appear to perform the same function.
All names follow a consistent noun_operation pattern (templates_list, project_generate), with minor inconsistency between plural 'templates_list' and singular 'template_preview'.
Six tools is a well-scoped count for a template/project generation server, covering the core workflow without unnecessary bloat.
The surface covers template discovery and project lifecycle basics (generate, status, validate, benchmark), but lacks explicit project update/delete operations, which agents may need for full lifecycle management.
Maintenance
Related MCP Connectors
Manage Pipefork API projects, drafts, connections, secrets, and deployments through MCP.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Your prompt library in any MCP client: list, fetch, save and version prompt templates.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- FlicenseBqualityDmaintenanceA production-ready MCP server template that enables developers to quickly build and deploy MCP servers with dynamic tool/resource loading, YAML-based prompts, and seamless OpenShift deployment. Supports both local development with hot-reload and production HTTP deployment with optional JWT authentication.1-
- AlicenseAqualityDmaintenanceExposes the Agentic Patterns Catalog as MCP resources and tools for AI coding agents to search, retrieve, and recommend patterns, recipes, frameworks, methodologies, and anti-patterns.121MIT
- FlicenseNot gradedqualityDmaintenanceEnables project creation with validated flow and automatic registration via MCP, supporting scaffold, bootstrap, and validation tools.-
- AlicenseNot gradedqualityDmaintenanceScaffolds new project directories from built-in templates for Python, Node.js, and Go via MCP tools.MIT