Skip to main content
Glama
Cybing521

Vensim MCP

by Cybing521
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Vensim MCP

No user-submitted related servers found.

    Related Servers

    • Astah MCP

      g0mz
      F
      license
      A
      quality
      C
      maintenance
      Local MCP server that converts modeling exercise requests into native Astah projects (.asta), supporting multiple UML diagram types with automatic layout and visual validation.
      6
      -

    • Xcos MCP

      gonced8
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      11
      GPL 3.0

    • file-conversion

      jmcneil86043
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for converting between everyday file formats (CSV, Excel, Markdown, Word), including a GxP-compliant Markdown to Word template. Exposes four conversion tools over stdio.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources