Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OurFamilyWizard MCP

No user-submitted related servers found.

    Related Servers

    • clio-mcp

      evanwillistech
      F
      license
      Not graded
      quality
      C
      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.
      -

    • whoop-mcp

      souravpn
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that gives Claude access to your WHOOP biometric data — recovery, sleep, strain, and workouts.
      28 npm
      MIT

    • Withings MCP Server

      akutishevsky
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.
      41
      MIT
    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.7/5.0

    Scored across 25 tools

    Disambiguation3/5

    Most tools have distinct resource-action targets, but the messaging cluster is dense: list_messages, get_unread_sent, list_drafts, status, check_freshness, and sync_messages all overlap around reading or verifying message/draft state. The long descriptions help, but an agent could easily pick the wrong freshness or listing tool.

    Naming Consistency4/5

    The overwhelming majority follow an ofw_verb_noun pattern, e.g. create_event, list_expenses, send_message, delete_draft. A few deviations like ofw_status, ofw_healthcheck, and ofw_get_unread_sent break the pattern slightly, but the convention is still predictable and readable.

    Tool Count3/5

    25 tools sits at the heavy end of the borderline range. The broad domain justifies a decent number, but roughly half the surface is dedicated to messaging/drafts, making the set feel larger and more redundant than necessary.

    Completeness3/5

    Calendar and messaging lifecycles are well covered, but journal entries only support create/list and expenses lack update/delete, leaving obvious CRUD gaps. There is also no single-event get, though the date-range list partially mitigates that.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources