jgs-magic-sysmlv1-mcp
Related Servers
Alternatives to jgs-magic-sysmlv1-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceAn MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.2-
- AlicenseNot gradedqualityAmaintenanceConnect Claude AI to Dassault Systemes CATIA V5 via the Model Context Protocol (MCP). Drive CATIA V5 CAD modeling from Claude Desktop or Claude Code using natural language.97MIT
- FlicenseNot gradedqualityBmaintenanceDrive Autodesk Revit, AutoCAD & Civil 3D from Claude over MCP — 190+ real actions, runs locally.2-
- AlicenseNot gradedqualityBmaintenanceThis MCP Server bridges Egonex-AI/Understand-Anything with Claude Desktop and other MCP clients, giving LLMs native access to full-codebase structural graphs, architecture analysis, and CI/CD validation.36 npmMIT
- AlicenseNot gradedqualityCmaintenanceA secure, local communication runtime bridge that interfaces a cloud-based Large Language Model (Claude Desktop) with a local machine execution environment using the Model Context Protocol (MCP).Eclipse Public 2.0
- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
TDQS
Scored across 133 tools
There is direct overlap between the generic create_element factory and roughly 20 specialized create_* tools, so agents face ambiguity about which to call. Generic set_property also overlaps with domain-specific setters like set_requirement_id, and the many Phase B diagram stubs add further confusion.
The vast majority of tools follow a clean verb_noun snake_case pattern such as create_block, set_multiplicity, and add_satisfy. A few outliers like ping, undo, redo, search, and impact_analysis break the pattern, but there is no mixed casing or chaotic convention.
133 tools is an extreme number for any MCP server, especially when many are Phase B stubs and the generic create_element tool duplicates numerous specialized create_* variants. Even for a broad SysML v1 modeling surface, this count would be far more manageable around 40-60 consolidated tools.
The tool set covers a broad range of SysML v1 modeling: blocks, requirements, ports, flows, state machines, activities, sequences, diagrams, stereotypes, validation, and model metrics. However, there are notable gaps such as no create_parameter or create_operation tools, no delete_diagram, and many diagram symbol operations are explicitly stubs.