Dynamo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DYNAMO_MCP_HOST | No | Host to bind to | localhost |
| DYNAMO_MCP_PORT | No | Port to bind to | 3000 |
| DYNAMO_MCP_BASE_DIR | No | Base directory for templates and virtual environments | ~/.dynamo-mcp |
| DYNAMO_MCP_TRANSPORT | No | Transport type (sse or stdio) | sse |
| DYNAMO_MCP_VENVS_DIR | No | Directory for virtual environments | ~/.dynamo-mcp/venvs |
| DYNAMO_MCP_AUTH_ENABLED | No | Enable authentication | false |
| DYNAMO_MCP_AUTH_PASSWORD | No | Authentication password | password |
| DYNAMO_MCP_AUTH_USERNAME | No | Authentication username | admin |
| DYNAMO_MCP_TEMPLATES_DIR | No | Directory for templates | ~/.dynamo-mcp/templates |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| templates_listC | templates list |
| template_previewD | template preview |
| project_generateA | Generate bundled inert project under operator private root; local opt-in required. |
| project_statusC | project status |
| project_validateD | project validate |
| project_benchmarkC | project benchmark |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Dynamo execution policy |
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.