A
licenseA
qualityA
maintenanceConnects Claude to OurFamilyWizard for natural-language access to co-parenting messages, calendar, expenses, and journal.
10
421 npm
MIT
OFW MCP
by chrischall
Related Servers
Alternatives to OFW MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables natural-language access to OurFamilyWizard co-parenting data, including messages, calendar, expenses, and journal entries.25279 npmMIT
- AlicenseAqualityAmaintenanceEnables natural-language access to OurFamilyWizard for co-parenting messages, calendar, expenses, and journal.13571 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
- AlicenseNot gradedqualityCmaintenanceConnects Claude to Microsoft Outlook through the Microsoft Graph API, enabling email management (list, search, read, send) and calendar operations (list, create, accept, decline, delete events) via OAuth 2.0 authentication.1MIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation4/5
The dedicated tools target clearly separate resources: resolving a link, finding nearby restaurants, fetching a menu, loyalty, orders, wallet. The only overlap is toast_graphql, which by design can reach everything the other tools cover, but its description frames it as an exploration escape hatch rather than a peer.
Naming Consistency5/5
Every tool carries the toast_ prefix and follows the verb_noun pattern (resolve_restaurant, find_restaurants, get_menu, list_orders, get_order, get_wallet, get_loyalty), with only the meta-tools toast_graphql and toast_healthcheck omitting a verb, which is natural for them.
Tool Count5/5
Nine tools is well within the ideal range for this domain, and each one earns its place: discovery, resolution, menu, order history/receipt, loyalty, wallet, plus a GraphQL escape hatch and a diagnostic tool.
Completeness4/5
The read surface is well covered end-to-end: find a restaurant, resolve its GUID, read the menu, list and fetch past orders, check loyalty and Toast Cash. Write operations are intentionally absent (mutations refused), and toast_graphql covers any remaining gaps, so there are no real dead ends.
Maintenance
ActivityMaintained
ResponsivenessResponsive