waro-mcp
Related Servers
Alternatives to waro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to interact with Odoo 17 ERP via external API, providing tools for inventory management, sales order processing, and customer management through natural language.-
- AlicenseAqualityCmaintenanceEnables Claude to inspect a WooCommerce store's orders, products, customers, stock, and sales summaries, with optional write tools for stock quantities and order statuses.91MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with WooCommerce stores through the WordPress REST API. It provides tools for managing products, orders, customers, shipping, taxes, coupons, reports, and store settings.MIT
- FlicenseDqualityDmaintenanceEnables interaction with a restaurant FastAPI backend for menu management, order processing, customer management, and analytics through natural language.241-
- AlicenseAqualityDmaintenanceEnables LLMs to interact with WhatsApp via the official WhatsApp Cloud API, providing tools for sending messages, templates, media, and managing conversations.1315 npmMIT
- AlicenseAqualityDmaintenanceExposes the Loyverse API as MCP tools to manage stores, products, inventory, customers, receipts, and more from AI assistants.54MIT
TDQS
Scored across 26 tools
Several tools have overlapping analytics purposes (analytics_waros, analytics_rfm, analytics_churn_risk, analytics_food_cost, analytics_alerts, analytics_data_quality, analytics_cohort, analytics_menu) but each targets distinct metrics. Some confusion possible between waros_estimate and waros_balances/customer, and between sales_list/metrics/detail and customers_orders, but descriptions are specific enough. However, sales_list vs sales_detail are clear, and customers_orders vs customers_list/detail are distinct. The overlap in analytics tools is moderate, but not severe.
The naming follows a general pattern of domain_subject, e.g., 'analytics_*', 'waros_*', 'queries_*', 'sales_*', 'customers_*', 'menu_*'. This is fairly consistent, but there are some deviations: 'waro_schema' and 'waro_ping' use a different prefix than the 'waros_*' group, and mixed order in 'financial_products'. The pattern is mostly predictable but has minor irregularities.
26 tools is slightly heavy but within the range for a comprehensive business analytics server covering multiple domains (analytics, sales, customers, menu, WAROS, queries). The count is high but each tool appears purpose-specific and covers a broad domain, so it's acceptable. Not excessive like 50+.
The tool surface covers a wide range of business analytics: sales, customers, menu, WAROS, financial metrics, queries. It includes list/detail/metrics and analytics for major areas. However, there are some gaps: no tool for updating/creating data (though analytics servers are often read-only), no explicit tool for user management or settings, but for the intended purpose of analytics and reporting, it seems fairly complete. There is also a queries_run and queries_schema for custom queries, which adds flexibility.