Skip to main content
Glama

Related Servers

Alternatives to ofw-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A4.1/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clear distinct purposes (messages vs. drafts vs. events vs. expenses vs. journal vs. attachments). A few overlaps exist: ofw_list_messages vs. ofw_list_drafts vs. ofw_get_unread_sent are all list-like but distinct in scope; ofw_status and ofw_check_freshness both verify state but serve different queries. Descriptions help disambiguate, leaving minimal confusion.

    Naming Consistency5/5

    All tools consistently follow the `ofw_<verb>_<noun>` snake_case pattern. Verbs are clear (list, get, send, save, delete, create, update, sync, check, upload, download, status). No mixed conventions or vague verbs — the naming is highly predictable.

    Tool Count4/5

    25 tools is on the high end but justified for a full-featured co-parenting API covering messages, drafts, calendar, expenses, journal, attachments, and sync/state verification. Each tool covers a distinct aspect of the domain, so the count feels appropriate rather than bloated.

    Completeness3/5

    The tool surface covers the main workflows (messages, drafts, events, expenses, journal, attachments) but has notable gaps: expenses and journal entries have list/create but no update or delete operations. Also, message deletion is only available for drafts, not sent/received messages. This limits lifecycle management for some domains.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues