No user-submitted related servers found.
Scored across 142 tools
Most tools are clearly distinguished by resource and HTTP method encoded in the name (e.g., get/delete/create on distinct domain objects), and descriptions add permission and behavior detail. However, the sheer number of similar endpoints—especially dashboard aggregates, material previews/downloads, and rundown execution controls—creates real selection friction for an agent.
Every tool follows the same anon_<method>_<resource_path>_<identifier> snake_case pattern, derived predictably from the underlying REST route. The convention is uniform across all 142 tools with no mixing of camelCase or vague verbs.
142 tools is an extreme surface that vastly exceeds practical agent navigation, far beyond the 25+ threshold. While the underlying API is broad, exposing essentially every REST endpoint as a separate MCP tool creates overwhelming choice and high misselection risk.
The surface provides deep multi-module lifecycle coverage: CRUD for stages, milestones, todos, materials, physical inventory, finance, lostfound, announcements, roles, members, risks, work modules, rundowns, signups, accounts, and custom tools, plus execution and sharing flows. Only very peripheral operations like project creation/deletion are absent, which is appropriate for a project-scoped API-key context.