A
licenseA
qualityA
maintenanceEnables natural-language access to OurFamilyWizard co-parenting data, including messages, calendar, expenses, and journal entries.
25
279 npm
MIT
OurFamilyWizard MCP
by chrischall
Related Servers
Alternatives to OurFamilyWizard MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceConnects Claude to OurFamilyWizard for natural-language access to co-parenting messages, calendar, expenses, and journal.10421 npmMIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.28139 npm14MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.11538 npm1MIT
- -licenseAqualityNot gradedmaintenanceEnables management of Cozi Family Organizer shopping lists and todo lists through natural language. Supports creating, editing, and organizing family lists with real-time sync to the Cozi platform.9-
- AlicenseAqualityAmaintenanceEnables AI assistants to manage Cozi Family Organizer accounts, including creating and updating shopping/todo lists, managing calendar appointments, and accessing family member information.15146 npm6MIT
TDQS
A3.7/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target distinct resources (trails, reviews, photos, weather, lists), but several begin with 'alltrails_get_trail' and could be confused: get_trail vs get_trail_gpx, get_trail_reviews, get_trail_photos, get_trail_weather. Descriptions clarify the specific output, but the prefix overlap creates some ambiguity.
Naming Consistency4/5
Tools consistently use snake_case with 'alltrails_' prefix and verb_noun structure (get_trail, list_user_lists, search, resolve_location). Slight inconsistency: 'alltrails_search' lacks an object (search what?), and 'alltrails_healthcheck' deviates from verb_noun pattern.
Tool Count4/5
13 tools is within a reasonable range for an AllTrails integration covering trails, user data, and diagnostics. However, some tools like healthcheck mix operational concerns with domain tools, and a few (e.g., get_trail_weather) could be folded into get_trail with a parameter.
Completeness3/5
Core reads (trails, lists, completed, feed) are present, but the surface lacks write operations: no create/update/delete for lists, no marking trails completed, no posting to feed. For a signed-in user integration, these gaps will cause agent failures for common tasks.
Maintenance
ActivityActive
ResponsivenessResponsive