Related Servers

Multiple tool clusters have unclear boundaries: time_create_time_entry, time_create_user_time_entry, and time_create_project_time_entry all appear to log time, and projects_create_assignment, projects_create_project_assignment, and projects_create_user_assignment are three near-identical creation paths. Similarly projects_get_project_phase vs projects_list_project_phases is fine, but admin_list_expenses/admin_get_expense vs time_list_approvals/time_create_approval blur the reporting vs approval boundary. An agent would frequently need to read long caveat text to pick correctly, which is a symptom of overlap rather than distinct purpose.

Nearly all names follow a predictable prefix_verb_noun convention (time_*, projects_*, admin_*) making the domain grouping obvious. A few workflow-style names like time_reconcile_and_submit_week or projects_clone_project_schedule deviate from the strict verb_noun shape, but the overall pattern is stable and readable.

104 tools is an extreme surface for a single MCP server, far beyond what an agent can scan or select from reliably. Much of the volume comes from parallel CRUD variants and undocumented-route shims rather than distinct capabilities.

Coverage is broad: CRUD for projects, phases, assignments, users, roles, disciplines, clients, contacts, leave types, holidays, expenses, categories, tags, custom fields, webhooks, plus time entry workflows and reports. Minor gaps exist (no update_holiday counterpart for some entities is present, but tags and expense categories lack update operations, and reports are read-only), though core lifecycle operations are well represented.