Vensim MCP
Related Servers
Alternatives to Vensim MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables agents to build, validate, calibrate, and export versioned scientific models with mandatory units, dimensional and numerical checks, and uncertainty analysis over stdio. Models can be simulated and exported to portable formats such as SBML, CellML, and Modelica.324 npm551 PyPI9MIT
- FlicenseAqualityCmaintenanceLocal MCP server that converts modeling exercise requests into native Astah projects (.asta), supporting multiple UML diagram types with automatic layout and visual validation.6-
- AlicenseBqualityBmaintenanceEnables controlling a local Scilab/Xcos installation to discover installed block libraries, create native block templates, read, write, and validate diagrams, and run simulations of arbitrary positive duration that return named numerical signal series. It exposes these capabilities as MCP tools over stdio or streamable HTTP, with model file access restricted to configured filesystem roots.11GPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server for rendering Object-Process Methodology (OPM) models from YAML to SVG diagrams and OPL sentences, with validation and generation capabilities.1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for converting files between different formats5MIT
- AlicenseNot gradedqualityAmaintenanceA stateless MCP server for composing, validating, auditing, and rendering consequential documents from a small semantic model.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct action: environment detection, model generation, inspection, validation, rendering, opening, and script creation. There is no overlap in purpose or output, making tool selection unambiguous.
Most tools follow the `verb_vensim_noun` pattern (generate_vensim_model, inspect_vensim_model, etc.), but `vensim_doctor` deviates by being a noun-first name without a clear verb. This is a minor inconsistency, not a chaotic mix.
Seven tools is a well-scoped size for a domain-specific integration. Each tool covers a necessary workflow step without redundancy, fitting comfortably within the ideal range.
The surface covers the primary lifecycle: create (generate), read (inspect), validate, preview (render), and open. Missing update/delete operations are acceptable since models are generated from JSON specs, and there is no simulation tool, but the core use cases are well addressed.