No user-submitted related servers found.
Scored across 89 tools
The tools are mostly organized around distinct resources and actions, so an agent can usually tell a project tool from an estimate, invoice, or change order tool. Some boundaries blur around time tracking (get_clock_status, list_time_cards, get_time_card, list_project_crew_hours) and contacts versus leads, though the descriptions provide enough context.
Every tool name uses snake_case with a verb_noun structure. Verbs such as get, list, create, update, delete, add, remove, send, and record are used predictably by operation type.
With 89 tools, the server is far beyond a typical well-scoped MCP surface and risks overwhelming tool selection. Even for a broad construction ERP domain, this level of granularity is too large for a single cohesive tool set.
Core financial workflows such as estimates, invoices, change orders, and payments have strong lifecycle coverage. However, many modules have notable dead ends: punchlists cannot add items, files cannot be uploaded, and submittals, RFIs, contacts, leads, opportunities, bills, purchase orders, and sub-contracts lack key update, delete, or send operations.