Skip to main content
Glama

Related Servers

Alternatives to Dawarich MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes read-only location history and related data from Dawarich via MCP tools, designed to run behind an OAuth-terminating proxy.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Minimal read-only MCP server that lets you query a Dawarich instance for stats, timeline, visits, points, track details, exports, reverse geocoding, and journey summaries.
      9
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables local, read-only access to Garmin Connect training and wellness data, including activities, sleep, HRV, and daily summaries, for client-side analysis through stdio.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables logging, listing, updating, deleting, and summarizing timesheet entries, starting and stopping timers, checking timer status, and exporting time data through natural language, backed by a local SQLite database.
      8 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools are clearly distinct: places, visits, points, timeline, stats, and recalculate all have separate purposes. However, the three trip tools (create/update/delete) are functionally identical stubs that all report an API gap, making them hard to distinguish by action despite different names.

    Naming Consistency5/5

    All tools follow a consistent dawarich_<verb>_<noun> pattern in snake_case, with verbs like search, find, create, update, delete, add, merge, and bulk_update. This is highly predictable and readable.

    Tool Count4/5

    At 19 tools, the server is slightly over the ideal 3-15 range but still reasonable for a domain covering places, visits, points, trips, stats, timeline, and map context. The three non-functional trip tools could be trimmed, but the count is not excessive.

    Completeness3/5

    Core place/visit/point operations are well represented, plus useful extras like timeline, stats, and map context. However, trip tools are non-functional stubs that only report an API gap, creating dead ends for trip workflows, and there is no delete_visit tool. These are notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues