BOS MCP Server
Related Servers
Alternatives to BOS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceMCP server that exposes ERP functionalities to AI agents, enabling read-only queries for sales orders and inventory, and human-in-the-loop purchase requisition creation and approval.59-
- AlicenseNot gradedqualityDmaintenanceMCP server integrating with Odoo ERP systems, enabling AI assistants to interact with Odoo data and functionality through tools and resources.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI platforms to search products, customers, and warehouses, and prepare and submit sales orders to a fixed ERP endpoint with per-session bearer authentication.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query ERP sales data, including employees, sales, customers, and top products, through MCP tools.-
- AlicenseBqualityBmaintenanceMCP server that connects AI assistants to the Conexa business management system, enabling CRUD operations on sales, customers, plans, contracts, charges, and more via 83 tools.83121 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with Odoo ERP apps like Inventory, CRM, Sales, and Manufacturing. It allows users to read, create, and manage Odoo records and workflows using natural language commands.2511 npm1ISC
TDQS
Scored across 108 tools
While each tool has a clear description, the high number (108) and overlapping domains (e.g., multiple list and search tools) create potential confusion. Agents might struggle to select the correct tool among many similar ones, especially with mixed language descriptions.
All tools follow a consistent 'bos_<domain>_<action>' pattern in snake_case. Verbs are predictable (list, create, update, delete, get, search, show), making navigation easy despite the large set.
108 tools is far too many for a single MCP server. It attempts to cover an entire retail/ERP system, including CLI commands, smart analytics, and administrative functions. The tool surface should be split into multiple focused servers (e.g., orders, products, customers, admin).
The tools cover the core lifecycle for most domains: customers (CRUD + addresses), products (CRUD + variants), orders (full workflow), cart/checkout, inventory, and more. Minor gaps exist (e.g., no category management beyond listing), but overall it's comprehensive for a retail system.