acu-mcp
Related Servers
Alternatives to acu-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceProvides live, near-real-time read access to Restaurant365 OData API for financial and operational data queries.8-
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to retail ERP data through the official output WebService, letting users query products, stock and inventory, customers and suppliers, sales movement and billing, orders, salespeople, and store information with date-window and store filters.MIT
- AlicenseAqualityBmaintenanceEnables querying and acting on any Acumatica ERP tenant's contract-based REST API through 8 generic tools, covering all entities with read-only by default safety.8MIT
- FlicenseBqualityDmaintenanceEnables read-only access to FileMaker databases through the Data API, allowing users to retrieve records, analyze metadata, search across layouts, and infer relationships while maintaining data security.16-
- AlicenseBqualityCmaintenanceEnables read-only access to Epicor Kinetic ERP data, including sales orders, customers, parts, and shipments, through secure MCP tools.4MIT
- AlicenseAqualityAmaintenanceEnables read-only access to Google Ads data through GAQL queries, resource exploration, recommendations, keyword planning and forecasts, and change history across manager and customer accounts.11MIT
TDQS
Scored across 16 tools
Most tools follow a clear get/query/list pattern with distinct resource scopes, but the specialized query tools (query_sales_orders, query_invoices, etc.) overlap functionally with the generic query_odata tool, which can access the same data. The descriptions help, but an agent might still be unsure which to use for a particular task.
Tool names are mostly consistent with a verb_noun pattern (get_* for single entities, query_* for filtered lists, list_* for enumerations). However, 'list_inventory_items' breaks the query_ convention used for similar list operations, and the OData tool naming mixes 'list' and 'query' for related actions.
16 tools is slightly above the typical 3-15 range, but the breadth is justified for an ERP system covering multiple modules (sales, shipping, invoicing, purchasing, inventory, customers) plus generic OData access. The count feels reasonable for the stated scope.
The tool set provides comprehensive read/query coverage for key Acumatica resources, and the generic OData tools fill gaps for any entity not covered by specialized wrappers. The main gap is the absence of write operations, but the descriptions emphasize analytics and reporting, making a read-only surface likely intentional.