aras-plm-mcp
Related Servers
Alternatives to aras-plm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to interact with Aras Innovator PLM systems via OAuth 2.0, allowing users to query PLM data, create items, and call server methods through natural language.16MIT
- FlicenseNot gradedqualityFmaintenanceIntegrates with Teamcenter PLM using its REST API, enabling search, create, update, and query of Teamcenter items through natural language.3-
- AlicenseBqualityDmaintenanceIntegrates PTC Windchill and Creo Parametric with LLM-based clients via the Model Context Protocol, enabling natural language interaction with PLM and CAD systems for tasks like part search, BOM retrieval, model operations, and exports.114MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IBM Engineering Lifecycle Management (ELM), including DOORS Next Generation, EWM, and ETM, for managing requirements, work items, tests, and project builds through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language interaction with KiCad projects, schematics, and PCBs, supporting project management, design rule checking, netlist extraction, and datasheet RAG search.2MIT
- AlicenseNot gradedqualityFmaintenanceProvides access to Autodesk Platform Services API, enabling interaction with ACC projects and issues through natural language.25MIT
TDQS
Scored across 71 tools
Most tools are clearly scoped to a specific resource and action, and the descriptions are rich enough to separate queries, lifecycle, workflow, BOM, and admin operations. However, a few pairs are genuinely confusable—aras_promote_item vs aras_release_item and aras_create_item vs aras_create_part/aras_create_document—so it is not a perfect 5.
The aras_ prefix plus a verb_noun structure is used consistently across nearly all tools, with clear clusters like get_*, list_*, create_*, and manage_*. A handful of nonstandard names such as aras_how_to, aras_where_used, aras_bulk_update, and bare verbs like aras_search or aras_ping keep it from being fully consistent.
71 tools is far beyond the 50+ extreme threshold and dramatically more than the recommended agent-facing surface. Even for a broad PLM domain, this many entry points creates a heavy selection burden, and many niche administrative tools could be consolidated or exposed behind a smaller number of parameterized tools.
The surface is exceptionally comprehensive: item CRUD, revisions, lifecycle, workflow, BOM, change management, documents/files, permissions, admin, reporting, and AML are all covered. Minor gaps remain, such as no direct file upload path, no generic relationship delete/update tool, and aras_run_query being a known-limited fallback, but these are documented and usually workaroundable.