iqms-mcp
Related Servers
Alternatives to iqms-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that connects to Oracle databases, enabling execution of registered and ad-hoc SQL queries, retrieval of business object details, and discovery of capabilities over stdio, HTTP/SSE, and REST transports.-
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating manufacturing systems (MES/ERP/quality/maintenance) with LLM agents, enabling event ingestion, incident triage, approval workflows, and RAG-based knowledge retrieval.MIT
- AlicenseNot gradedqualityDmaintenanceThis project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Oracle SCM (beta): https://www.cdata.com/download/download.aspx?sku=KSZK-V&type=betaMIT
- FlicenseNot gradedqualityCmaintenanceEnables querying Proluxe ERP data such as customers, orders, invoices, AR aging, bills of materials, product catalog, focus priorities, and projects through MCP tools.1-
- AlicenseNot gradedqualityAmaintenanceUniversal MCP server for readonly-first access to Oracle, SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, and Qdrant vector search.41 npm1MIT
- AlicenseBqualityCmaintenanceEnables read-only access to Epicor Kinetic ERP data, including sales orders, customers, parts, and shipments, through secure MCP tools.4MIT
TDQS
Scored across 16 tools
Several tools have overlapping purposes, such as the domain-named tools (workorders, inventory, boms) which duplicate functionality already provided by specific prefixed tools like iqms_workorders_list, iqms_inventory_onhand, etc. This creates ambiguity about which tool to use.
Naming is inconsistent: tools have either a 'iqms_' prefix with snake_case (e.g., iqms_boms_explode) or no prefix and just a noun (e.g., workorders, inventory). Additionally, some tools use verbs (list, get, create) while others are simply domain names.
With 16 tools, the count is slightly above the typical 3-15 range but still reasonable for an ERP system covering multiple domains. The overlap reduces efficiency but does not make the count inappropriate.
The tool set covers basic retrieval and creation for several domains but lacks update, delete, and other lifecycle operations. For example, sales orders and purchase orders only have list tools, and no tools exist to modify or close records.