OurFamilyWizard MCP
Related Servers
Alternatives to OurFamilyWizard MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.251,216 npm10MIT
- AlicenseAqualityAmaintenanceConnects Claude to OurFamilyWizard for natural-language access to co-parenting messages, calendar, expenses, and journal.10598 npmMIT
- AlicenseAqualityBmaintenanceEnables natural-language access to OurFamilyWizard co-parenting data, including messages, calendar, expenses, and journal entries.251,216 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.589 npm59MIT
- FlicenseNot gradedqualityCmaintenanceA 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.32 npmMIT
TDQS
Scored across 11 tools
Most tools map cleanly to distinct actions: active vs sold, search vs detail, individual vs aggregate, and lookup vs calculation. The main overlap is `hemnet_get_listing_photos`, which duplicates the gallery photo URLs already returned by `hemnet_get_listing`, though the descriptions make the intended use fairly clear.
All tools share the `hemnet_` prefix and snake_case with a generally verb-first pattern (`get_`, `search_`, `compare_`, `calculate_`). Minor deviations like `hemnet_healthcheck` and `hemnet_get_by_address` break the strict verb_noun pattern but do not hurt predictability.
At 11 tools, the surface is well-scoped for a read-only property platform: location autocomplete, active/sold search, detail views, comparison, market stats, mortgage calculation, address resolution, and health diagnostics. The count is within the ideal range and each tool has a discernible role.
The set covers the main Hemnet workflows end to end: find location IDs, search active and sold listings, retrieve full details for both, compare listings, aggregate market stats, resolve addresses, and estimate mortgage costs. There are no obvious dead ends for a read-only property-research MCP.