/m:os stock and flow mapper
Related Servers
Alternatives to /m:os stock and flow mapper
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConverts structured system dynamics specifications into Vensim .mdl files with layout, SVG preview, static audit, and native Vensim integration. It can be used as an MCP server or from the command line.7MIT
- AlicenseAqualityBmaintenanceEnables language models to turn structured diagram specifications and lightweight textual DSL into deterministic, fully editable Excalidraw scenes and standalone SVG files. Provides validated layered layout, crossing-reduced edge routing, schema conformance checking, and export through MCP tools over stdio.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables creating, importing and incrementally editing draw.io diagrams through structured tools that manage nodes, edges and groups, then render validated .drawio files. It keeps diagram state across turns, supports automatic layout and undo, and runs locally over stdio or HTTP so any MCP client can drive it.Apache 2.0
- AlicenseBqualityBmaintenanceMCP server that enables AI assistants to create, parse, render, and validate Draw.io diagrams programmatically.142MIT
- AlicenseAqualityAmaintenanceEnables MCP-capable agents to read, create, modify, align, distribute, organize and export local-first infinite whiteboard content, including sticky notes, text, shapes, arrows, ink, mind maps, images, files and links across multiple pages. Provides 16 tools over stdio or Streamable HTTP, plus resources and prompts, with version-conflict protection and audit trails so canvas edits never silently overwrite newer content.1620MIT
- AlicenseBqualityDmaintenanceMCP server that enables LLMs to create and edit draw.io diagrams using high-level intent commands, with automatic layout and styling.44 npm4MIT
TDQS
Scored across 5 tools
model_get and model_validate both validate and return the caller-supplied model, making their boundary unclear. model_create and model_update also overlap because both accept a complete model and the server is stateless, yet update is described as replacing an active visual model.
All tools follow a consistent model_verb pattern: model_create, model_update, model_validate, model_get, and model_export. The naming is predictable and clearly indicates the resource being operated on.
Five tools is a reasonable scope for a model validation/export helper. However, the overlap between create, update, get, and validate makes the set feel slightly larger than necessary.
The surface covers creation, update, validation, retrieval-like access, and export, but the stateless design means get is not true retrieval and there is no persistence lifecycle. Core model transformation workflows are mostly covered, but the lack of clear retrieval or reset behavior leaves notable gaps.