No user-submitted related servers found.
Scored across 18 tools
Each tool targets a distinct resource or action: search, activity, projects, folders, workflow statuses, time entries, todos, tasks, task history, comments, pages, people, attachments. List/get pairs are clearly differentiated by singular vs plural and explicit descriptions, so an agent can reliably select the right tool.
All tools use a consistent verb_noun pattern: list_* for collections, get_* for single items, plus quick_search and list_recent_activity which follow the same style. Snake_case is used throughout with no mixing of conventions, making the API predictable.
18 tools is on the higher end but still reasonable for a project management server covering many entity types (projects, tasks, todos, pages, people, folders, comments, time entries, attachments, activity). Each tool serves a distinct purpose and none feel redundant, though the count slightly exceeds the typical 3-15 sweet spot.
The tool surface is heavily read-focused: every entity has list/get operations but no create, update, or delete methods exist for any resource. For a project management domain, this is a significant gap, as agents cannot create tasks, update statuses, add comments, or modify anything, limiting practical workflows.