@aiotic/mcp
Related Servers
Alternatives to @aiotic/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read orders, stock, prices, contractors, payments, debts, and sales from SmartUp ERP, with optional write capabilities for creating and updating orders and contractors when explicitly enabled.19MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Odoo ERP systems through natural language to search records, create entries, update data, and manage business operations. Supports secure authentication and configurable access controls for production environments.Mozilla Public 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and execute Slingrs ERP endpoints for sales orders, inventory, production, purchasing, shipments, and custom entities through dynamically loaded OpenAPI tools.4 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business records like customers, products, and invoices across any Odoo instance.1Mozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to read and query SAP OData services and SAP Business One Service Layer data such as business partners, products, items, sales and purchase orders, and invoices, plus gated creation and updates. Writes are disabled by default, support dry-run payload preview, and are verified by an independent read-back, with credentials kept out of tool arguments and local mocks allowing the whole stack to be exercised without a SAP account.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and operate on ERP data through a unified tool interface, working across CSV exports, SFTP drop folders, SQLite/ODBC, and optional enterprise APIs. It supports purchase orders, vendors, and inventory lookups while keeping agent-facing tools consistent regardless of backend.MIT
TDQS
Scored across 28 tools
Most tools have clearly distinct resource/action targets, but the documentation/reference cluster (get_schema, get_example, get_endpoint, list_endpoints, get_page, search_guide) has enough conceptual overlap that an agent could occasionally pick the wrong retrieval tool. Customer/product/order CRUD and lifecycle tools are otherwise well separated.
Almost all tools consistently use snake_case verb_noun or verb_resource patterns (list_products, get_customer, upsert_product, delete_customer_product). The main minor deviation is tenant_health, which is noun-based rather than action-based.
At 28 tools, the surface is heavy for a single MCP server and exceeds the 25-tool threshold where tool count becomes cumbersome. While some breadth is justified by combining live API operations with documentation/reference tools, the set is still large enough to burden selection.
The server covers the core customer, product, customer-product, order, rejected-email, ERP-send, and documentation workflows with create/read/update/delete or equivalent lifecycle operations. Minor gaps remain, such as no explicit list_customers or get_customer_product tool, and bulk operations appear in schemas but are not surfaced as tools.