Skip to main content
Glama
Thecimal

Quantified Self MCP Server

by Thecimal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Quantified Self MCP Server

  • google-health-mcp

    partymola
    A
    license
    A
    quality
    A
    maintenance
    MCP server for the Google Health API: heart rate, activity, sleep, SpO2, HRV, ECG and irregular-rhythm notifications, read into a local SQLite cache for fast offline queries and trend analysis. OAuth 2.0 with automatic token refresh, incremental sync, a cache-only offline mode, and a doctor command that diagnoses a setup without spending quota.
    24
    202 PyPI
    1
    GPL 3.0

Related Servers

  • finanzas-pyme

    JuanDsm04
    F
    license
    A
    quality
    B
    maintenance
    Enables LLMs to answer small business finance questions about spending, sales trends, cash flow projections, and profitability using a local SQLite database.
    6
    -

  • mydata

    bibekg
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables querying personal data synced from services like Lunch Money and Strava using SQL via Claude.
    1 npm
    1
    MIT

  • mcp-sqlite-tools-plus

    MauricioPerera
    A
    license
    B
    quality
    D
    maintenance
    Enables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.
    26
    2 npm
    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

A4.4/5.0

Scored across 20 tools

Disambiguation5/5

Each tool has an explicit 'use this when / do not use this when' section that routes the agent to the correct alternative, and the overlapping candidates (read_health_data vs get_metric_history vs read_measurements, get_baseline vs calculate_metric_trend vs detect_metric_anomalies) are cleanly distinguished by scope. The read/write/log/aggregate/analytics split is unambiguous even for an agent scanning names alone.

Naming Consistency4/5

All names are snake_case verb_noun, but read-only tools mix 'read_*' (read_health_data, read_measurements) and 'get_*' (get_metric_history, get_baseline) with no clear rule distinguishing them, and some names append _csv or use long sub-verbs. Still predictable and readable, just not perfectly uniform.

Tool Count4/5

20 tools is on the heavy side, but the domain genuinely spans raw/aggregate reads, two logging paths, workout sessions, provenance, status/imports, and seven distinct analytics operations. Each tool covers a distinct capability rather than padding, so the count is justified, if slightly large.

Completeness4/5

The surface covers read/aggregate/log/clear for metrics plus workouts, provenance, data/import status, CSV export, and a full analytics suite (baseline, anomaly, trend, period compare, correlation, recent changes, explain). Minor gaps remain: no update/delete for individual measurements or workout sessions beyond clear_metric for daily metrics.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources