NM
Nexus MCP Server exposes a retail operations stack—CRM, orders, inventory, fulfillment, procurement—to AI agents through a single Model Context Protocol endpoint. Built for SME commerce teams running lean ops, it lets Claude, Cursor, or custom agents query and mutate operational data without bespoke API glue for each system. The multi-tenant design suits founders and CTOs who want one agent-accessible backend covering day-to-day retail workflows rather than stitching point tools together.
> what it does
- Exposes CRM, orders, inventory, and fulfillment over one MCP endpoint
- Supports multi-tenant deployments for agencies managing several retail clients
- Connects directly to Claude Desktop, Cursor, and custom agent clients
- Handles procurement and supplier workflows alongside customer-facing order data
- Open-source on GitHub, self-hostable for teams with data residency needs
> also under
> how nexus mcp server compares
bidirectional editorial> alternatives to nexus mcp server
by surface + editorial> nexus mcp server pairs well with
GorgiasAgent-driven ops backend plus customer-facing AI helpdesk covers both fulfillment and support conversations.paid
Tidio ‑ Live Chat & AI ChatbotTidio handles storefront chat and AI replies while Nexus exposes orders and inventory to agents.freemium
eDesk ‑ AI, Helpdesk & ChateDesk gives multi-channel support automation; Nexus supplies the operational data agents need to resolve tickets.paid