No user-submitted related servers found.
Scored across 25 tools
Most tools target distinct resources and actions, with clear separation between listing, mutating, and CUA-driver operations. Minor confusion is possible between openmausbot_api_health and openmausbot_status, and between the generic openmausbot_plan and the per-resource 'plan or apply' mutation tools, but descriptions mostly mitigate this.
All tools share the openmausbot_ prefix, which helps, but verb patterns are mixed: list_bots vs get_companion_settings vs usage vs status, and cua_skills_status/cua_permissions_status/cua_check_update deviate from the list_/set_ convention. The naming is readable but not uniformly predictable.
At 25 tools, this sits at the heavy end of the acceptable range. The count is somewhat justified by covering bot management, routines, webhooks, usage, companion settings, and the CUA-driver surface, but it feels like several smaller logical servers have been merged into one.
Routine lifecycle is well covered with upsert, enable/disable, run, and delete, and companion settings have get/set. However, webhooks are list-only with no create/update/delete, bots lack create/delete, and the CUA-driver tools only inspect and invoke rather than manage the driver itself, leaving notable gaps.