health-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTPモードのリッスンポート | 3000 |
| TRANSPORT | No | http で Streamable HTTP サーバーとして起動 | stdio |
| MCP_AUTH_TOKEN | No | 設定すると /mcp にBearer認証を要求。claude.aiカスタムコネクタは静的トークン未対応のため通常は空 | |
| HEALTH_API_BASE_URL | No | health-ojimpo バックエンドのベースURL(Docker内は http://backend:8000) | http://localhost:8400 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_statusA | Get the current snapshot of the personal health dashboard (health.ojimpo.com): overall health score/status (NORMAL/CAUTION/CRITICAL) and cultural activity score/status (RICH/MODERATE/LOW), per-category cards (this week vs previous week with change), condition state cards (sleep/readiness/stress/weight/outing/CTL), and trend comments. Scores are percentages of personal baselines (100 = baseline met). Use this first for any 'how am I doing' question. |
| get_score_historyA | Get the score time series: one row per date with overall health_score and cultural_score, plus optional per-category score columns. range 1m/3m = daily points, 1y = weekly points. Valid category names — activity: music, exercise, reading, movie, sns, coding, calendar, live, shopping, vitality, outing_activity, cd, podcast, game, like, study; state: sleep, readiness, stress, weight, outing, ctl. Add only the categories you need to keep output small. |
| get_recent_activitiesA | List the most recent concrete activities across all sources (e.g. tracks listened, workouts, movies watched, commits) as human-readable lines with relative time. The backend keeps the latest 8. |
| list_sourcesA | List all configured data sources with their category, display_type (activity/card_only/state), classification (baseline/event/health_only/both), status, and baseline (base_value per aggregation period). Use to discover valid 'source' and 'category' values for query_records. |
| query_recordsA | Query raw daily activity records (one row per date x source x category: minutes, raw_value, raw_unit). Requires a from/to date range (YYYY-MM-DD). Filter by source and/or category (see list_sources). For ranges over ~2 months prefer group_by week or month to keep output small; raw mode is capped by 'limit' and reports truncation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: snapshot status, recent activities, historical scores, source metadata, and raw data queries. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_current_status, list_sources, query_records), making the set predictable and easy to navigate.
Five tools is an appropriate scope for a health dashboard, covering key operations without being too sparse or overly heavy.
The set provides a complete view of health data: current status, recent activities, historical trends, source configurations, and raw data access. No obvious gaps for a read-only dashboard.