aas-mcp
Related Servers
Alternatives to aas-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 gradedqualityDmaintenanceMCP server for BESSER low-code platform enabling AI assistants to create, manipulate, and generate code from domain models through natural language. Supports model creation, deletion, and multi-language code generation (SQL, Python, Java, etc.) via the Model Context Protocol.8MIT
- AlicenseAqualityAmaintenanceAn MCP server that gives AI agents access to the full Cumulocity API surface through a compact code-mode interface.3354 npm6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server enabling AI assistants to perform CRUD operations on a Supabase database via a standardized interface.194MIT
- AlicenseNot gradedqualityBmaintenanceA config-driven MCP server that exposes OData and REST APIs as MCP tools, enabling AI assistants to query, manage, and monitor SAP backends through natural language.43 npm31MIT
- AlicenseAqualityCmaintenanceMCP server for Microsoft Dynamics 365 Business Central that enables AI assistants to query and manage Business Central data via full CRUD operations.67 npmMIT
TDQS
Scored across 25 tools
Most tools are clearly distinct, but update_submodel_element can also create elements, overlapping with create_submodel_element. Additionally, get_health_status and is_healthy serve similar purposes, which could cause confusion.
All tools follow a consistent verb_noun pattern, with plural forms for list operations (e.g., get_shells, get_submodels) and singular forms for specific items. The naming is predictable and uniform across the entire set.
With 25 tools, the server sits at the high end of the acceptable range. The domain is broad, but the count feels heavy, especially with multiple variants for value, metadata, and elements.
The tool set covers CRUD for all main resources: shells, submodels, submodel elements, and submodel references. Minor gaps exist, such as lacking an update operation for submodel references and metadata access for elements, but core workflows are well supported.