A
licenseA
qualityA
maintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.
11
843 npm
1
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.10686 npmMIT
- AlicenseAqualityAmaintenanceEnables natural-language access to OurFamilyWizard co-parenting data, including messages, calendar, expenses, and journal entries.25884 npmMIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that integrates Google Calendar with Claude Desktop, enabling users to manage calendar events (view, create, update, delete) through natural language.5110 npm59MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude (or any MCP client) to read and write Clio Manage data—contacts, matters, activities—directly from chat, with flat-fee billing support in one call.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that gives Claude access to your WHOOP biometric data — recovery, sleep, strain, and workouts.21 npmMIT
TDQS
A4/5.0
Scored across 28 tools
Disambiguation3/5
Most tools map to distinct resource+action pairs, but there is real overlap: ofw_list_drafts, ofw_status, and ofw_check_freshness all answer draft/message lifecycle questions, and ofw_list_messages vs ofw_get_message vs ofw_sync_messages blur the read path. The descriptions are extraordinarily verbose precisely to keep these apart, which signals the boundaries are not self-evident from the names alone.
Naming Consistency5/5
Every tool uses the ofw_ prefix with a consistent snake_case verb_noun pattern (ofw_list_*, ofw_get_*, ofw_create_*, ofw_update_*, ofw_delete_*). The convention is uniform across all 28 tools with no camelCase or stylistic deviations.
Tool Count3/5
At 28 tools this sits in the heavy range for a single server, and several tools (ofw_status, ofw_check_freshness, ofw_list_drafts) could plausibly be consolidated. The breadth of domains (messages, drafts, events, expenses, journal, attachments, diagnostics) justifies a large surface, but it leans over-scoped.
Completeness4/5
Core domains are well covered: events have full CRUD, expenses have list/create/update/totals/categories/receipt upload, messages have read/send/draft/sync/attachment flows. Minor gaps exist (journal has list/create but no update/delete; no message deletion), though these may reflect OFW constraints and are workable around.
Maintenance
ActivityActive
ResponsivenessResponsive