Skip to main content
Glama
Sign In
OurFamilyWizard MCP

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OurFamilyWizard MCP

No user-submitted related servers found.

    Related Servers

    • OFW MCP

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Connects Claude to an OurFamilyWizard account, enabling natural-language access to co-parenting messages, calendars, expenses, and journal entries — including reading folders and drafts, syncing, and creating events or messages with confirmation safeguards.
      9
      342 npm
      MIT

    • clio-mcp

      evanwillistech
      F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action (get_message vs list_messages vs sync_messages, create/update/delete_event, create/update_expense). The weak spot is the trio ofw_check_freshness / ofw_status / ofw_list_drafts, which all answer 'is this still a draft?' with overlapping live-lifecycle fields; the descriptions explicitly route between them, which mitigates but does not eliminate the overlap. ofw_upload_attachment vs ofw_upload_expense_pdf is also close, though the scope difference (message attachments vs expense receipts) is spelled out.

    Naming Consistency5/5

    Every tool uses the ofw_ prefix plus a consistent snake_case verb_noun pattern (get_/list_/create_/update_/delete_/upload_/download_/save_/sync_/mark_/check_). Compound nouns like ofw_list_journal_entries and ofw_mark_expense_reimbursed remain predictable and readable.

    Tool Count3/5

    30 tools is heavy in absolute terms, but the server legitimately spans five domains (messages/drafts, calendar, expenses, journal, attachments/diagnostics), so roughly 5-6 tools per domain is defensible. Still, some consolidation is possible (status/check_freshness/list_drafts, the two upload tools), making this borderline rather than well-scoped.

    Completeness4/5

    Strong lifecycle coverage: messages (read/list/sync/send plus full draft save/list/delete), calendar (list/create/update/delete/export), expenses (list/create/update/categories/totals/reimburse/upload receipt), and diagnostics/freshness. Gaps exist where the surface stops short of CRUD — journal entries have only list+create (no update/delete), and expense deletion is explicitly absent — but these are minor or upstream-constrained.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources