Skip to main content
Glama
Syncky Health

Syncky Health

Official

Related Servers

Alternatives to Syncky Health

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read your own Apple Health data through a self-hosted SQLite mirror, allowing them to query health metrics, workouts, meals, and strength logs without sending data to the cloud.
      56 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A remote MCP server that lets AI assistants such as Claude, ChatGPT, and any MCP client ask about a user's Apple Health data, with answers produced live by the user's iPhone via HealthKit. Health data is forwarded through process memory only — never written to disk — and covers sleep, workouts, metric series, health overviews, and user-defined custom metrics.
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Local-first MCP server that reads Apple Health export files (export.xml/zip) and exposes activity, sleep, HRV, and workout data to AI agents, keeping all data on your machine.
      18
      260 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Apple HealthKit → PostgreSQL sync + MCP server for Claude Code, Cursor, and Ollama. Open-source iOS app with reliable background sync (HKObserverQuery). 11 tools covering health summary, sleep, HRV trends, workouts, daily snapshots, metric stats, period comparison, and coaching briefs. Supports Supabase, Neon, and self-hosted Postgres. Privacy-first: your data goes to your own database.
      11
      9
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server that exposes Apple Health data (steps, workouts, sleep, etc.) from a local SQLite store, allowing AI agents to query health metrics without sending data to hosted services.
      9
      32
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: status is local metadata, inbox is read-only history, send writes to a confirmed phone, ack advances a receive checkpoint, and skill reads bundled docs. The main potential confusion is inbox vs. ack, but the descriptions explicitly state that reads never ACK, which resolves the boundary.

    Naming Consistency4/5

    All names share a consistent syncky_ prefix and single-word, lowercase style, making the set predictable. The only minor deviation is mixing nouns (status, inbox, skill) with verbs (send, ack) rather than a uniform verb_noun pattern.

    Tool Count5/5

    Five tools is a well-scoped surface for a relay-style messaging server: status, read, send, acknowledge, and skill retrieval. Each tool clearly earns its place with no redundant entries.

    Completeness4/5

    The core relay lifecycle (status, send, read history, acknowledge, skill docs) is covered, so agents can complete primary workflows. Minor gaps exist around message deletion/retention control and managing multiple confirmed phones or contacts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues