No user-submitted related servers found.
Scored across 50 tools
Most tools map cleanly to a resource+action, but several pairs overlap: novacrm_update_product explicitly updates stock while novacrm_adjust_stock exists for stock movement, novacrm_update_opportunity can plausibly change stage while novacrm_move_opportunity is the dedicated stage-mover, and novacrm_update_store overlaps with novacrm_set_store_status for open/closed and published state. Descriptions partially disambiguate, but an agent can still easily pick the wrong tool for a stage change, stock edit, or store status toggle.
The novacrm_ prefix plus verb_noun pattern (list_clients, get_order, create_task, update_proposal, delete_coupon-style) is applied across nearly all 50 tools. Minor deviations exist: novacrm_ping has no verb_noun form and novacrm_inventory_alerts is a bare noun rather than an action, and novacrm_complete_task / novacrm_move_opportunity use verbs outside the standard CRUD set (though still readable).
50 tools is heavy for any single MCP server, but the surface spans many distinct sub-domains (clients, products, orders, coupons, store, webhooks, automations, tasks, proposals, opportunities, analytics), each with only a handful of tools. The count is defensible by domain breadth but sits at the borderline where an agent's tool-selection context becomes unwieldy.
Core entities — clients, products, orders, tasks, automations, proposals, opportunities — have near-full CRUD/lifecycle coverage including delete and lifecycle actions like cancel, complete, and stage moves. Gaps remain: coupons have only list/create/validate (no update/delete) and webhooks have only list/create (no delete/update or rotation), which are minor but real dead ends.