No user-submitted related servers found.
Scored across 69 tools
Tools are grouped by clear domain prefixes (memory_, tasks_, skills_, routines_, session_) and most have distinct purposes. However, tasks_resolve and tasks_resolve_by_name are nearly identical in behavior, and the various memory delete variants (memory_delete, memory_delete_batch, memory_forget) create some boundary ambiguity.
Tool names consistently follow a [domain]_[action] snake_case pattern throughout the entire set, making the naming highly predictable. Even subdomains like memory_git_ and memory_snapshot_ preserve the same convention, so agents can infer behavior from name structure.
69 tools is an extremely large surface for an MCP server, far beyond the 25+ threshold that typically makes a set feel overloaded. While the breadth covers multiple subsystems, several tools are redundant (tasks_resolve vs tasks_resolve_by_name) and the sheer count will make tool selection slower and more error-prone for agents.
The server covers full CRUD/lifecycle for memory, spaces, projects, tasks, skills, routines, snapshots, and git sync, which is impressively comprehensive. Minor gaps exist, such as no way to delete a memory relationship, no comment update/delete, and no routine execution history listing, but these are workarounds.