Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Running Companion is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
Your own Garmin running and health data: readiness, runs, sleep, trends and patterns. Self-hosted.
Quickstart
Install it the way its author documents:
1. The Docker volume of your Running Companion install, where its database and settings are. Set it up first (see the README): this server reads that data, it doesn't create it.
The full guide: https://github.com/Dtsiakas/running-companion
Publishernot claimed
DTAll 1 server
dtsiakas1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Running Companion as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Install it the way its author documents:
1. The Docker volume of your Running Companion install, where its database and settings are. Set it up first (see the README): this server reads that data, it doesn't create it.
The full guide: https://github.com/Dtsiakas/running-companion
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Recovery status (green/amber/red with reasons), HRV, resting HR, sleep, training load (fitness/fatigue/form), last night in detail (score, stages, bedtime, breathing rate, SpO2), energy (Body Battery this morning, yesterday's stress), everyday activity (steps, calories, weekly intensity minutes),…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
One row per Monday-based week: runs, km, hours, load, intensity split, efficiency, fitness/form, weight, sleep, HRV, resting HR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weeks | integer | no | — |
Activities newest first, with pace, HR, load, intensity split, efficiency and RPE. Filter by date range, run category or activity type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | — |
| to | string | no | — |
| category | string | no | — |
| type | string | no | Substring of the activity type, e.g. 'running', 'treadmill', 'hiking' |
| limit | integer | no | — |
Everything about one activity: summary, running dynamics, zones, the planned workout steps, planned vs actual per step (executed_steps: auto-laps merged back into steps, pace judged against the target as on/fast/slow), every lap and best efforts. Defaults to the latest activity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | integer | no | — |
Fastest time for 400 m, 1 km, 1 mile, 3 km, 5 km, 10 km, half and marathon found inside any run. Optionally only since a date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | — |
A metric aggregated per week or month. Metrics: ${Object.entries(TREND_METRICS) .map(([name, metric]) =>
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | yes | — |
| period | string | no | — |
| from | string | no | — |
| to | string | no | — |
Schema of every table, units, how each derived metric is calculated, the HR thresholds in use and known caveats. Read before writing SQL.
No parameter schema on file.
Run one read-only SQLite SELECT against the database (max 200 rows). Call describe_data first for tables, units and conventions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sql | string | yes | — |
Fetch new data from Garmin (activities, sleep, HRV, wellness, weigh-ins) and recompute metrics. Usually takes 10–30 seconds.
No parameter schema on file.
Signals for a day (warnings such as possible illness, overreaching, load spikes; watch items such as easy-run drift, sleep debt, irregular bedtimes, stress streaks; positives) and the user's personal patterns: comparisons from two years of their own data (late bedtimes, short nights, hard…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| include_patterns | boolean | no | — |
The computed report for one Monday-to-Sunday week: a headline, training (volume against the previous four weeks, intensity balance, form), key sessions with planned vs actual, recovery (HRV, resting heart rate, status days, sleep against need, sleep score, bedtime regularity), life (stress, Body…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| week_start | string | no | — |
Weight trend against the user's goal with a safe-rate assessment and projected date, body composition (two-week averages of fat and muscle, a muscle-loss flag), Garmin's fitness age, calories burned on rest, training and big days, the user's own sweat rates (ml/h, overall and warm vs cool), and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| run_minutes | integer | no | — |
| hard | boolean | no | — |
Sleep: the last 4 weeks of nights (bedtime, wake time, hours, Garmin's sleep need, score), tonight's suggested bedtime (Garmin's need counted back from the usual wake time for tomorrow's kind of day, plus a realistic 30-minute step when the target is far from the usual bedtime), 7-night sleep…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
Hourly forecast for today's remaining hours and tomorrow (06:00 to 22:00) where the user usually runs, from Open-Meteo: air temperature, dew point, humidity, wind, chance of rain, and the heat cost of each hour (Hadley's temperature plus dew point rule: estimated % slower at the same effort). Each…
No parameter schema on file.
Lifetime totals, milestones passed with their dates (total km, run counts, first times under round times per distance), the next milestones with an estimated date at the recent pace, records (longest run, biggest week and month, weekly streaks) and personal bests per distance. Pass year for that…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | no | — |
| form | boolean | no | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under AGPL-3.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Running Companion or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.3.3.
0.3.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Running Companion can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.