Scored across 71 tools
Despite the large number of tools, each targets a distinct resource and action; reads, writes, analytics, comms, bookings, identity, and artifact-review operations are cleanly separated. Potentially similar pairs like list_ideas/list_insights and pm_meta/list_features are explicitly cross-referenced so an agent can tell them apart.
The overwhelming majority follow a consistent verb_noun pattern: list_*, get_*, create_*, update_*, analyze_*, with action verbs like merge, unmerge, vote, promote, and reschedule. Minor deviations like pm_meta and whoami break the pattern slightly, but they are isolated and easy to learn.
71 tools is an extreme number for a single MCP server, well above the 50+ threshold for a severe mismatch. Even though the tools are grouped by domain, the surface is very heavy for an agent to navigate and would be better split into focused servers such as PM, analytics, comms/support, identity, and bookings.
The core product-management lifecycle is well covered: features, tasks, sprints, objectives, key results, initiatives, ideas, experiments, releases, decisions, pages, and insights all have list/create/update flows, with archiving and status transitions replacing hard deletes. Minor gaps exist—no booking creation, no conversation reopen/assign, and no delete for most entities—but agents can work around them without dead ends.