timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Local-first Garmin data warehouse: sync once to SQLite, analyze trends and correlations offline.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 12/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 19/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Garmin Local MCP。按照 https://mcp.popnx.com/i/anup-shesh-garmin-local-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Garmin Local MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "garmin-local": { "command": "uvx", "args": [ "garmin-local-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Garmin Local MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"garmin-local": {
"command": "uvx",
"args": [
"garmin-local-mcp"
]
}
}
}用 Garmin Local MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Garmin Local MCP,或回答中出现 Garmin Local MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
GARMIN_MCP_DATA_DIR 本地数据仓库的数据目录(默认为 /.garmin-mcp) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Garmin Local MCP
Garmin Local MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Garmin Local MCP 的应用
B · 数据库与数据集 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Garmin Local MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user garmin-local -- uvx garmin-local-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Garmin Local MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user garmin-local -- uvx garmin-local-mcp应能看到 Garmin Local MCP 在列表中并显示已连接
用 Garmin Local MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Garmin Local MCP,或回答中出现 Garmin Local MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
GARMIN_MCP_DATA_DIR 本地数据仓库的数据目录(默认为 /.garmin-mcp) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Garmin Local MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "garmin-local": { "command": "uvx", "args": [ "garmin-local-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Garmin Local MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Garmin Local MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Garmin Local MCP,或回答中出现 Garmin Local MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
GARMIN_MCP_DATA_DIR 本地数据仓库的数据目录(默认为 /.garmin-mcp) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Garmin Local MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "garmin-local": { "type": "stdio", "command": "uvx", "args": [ "garmin-local-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Garmin Local MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Garmin Local MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Garmin Local MCP,或回答中出现 Garmin Local MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
GARMIN_MCP_DATA_DIR 本地数据仓库的数据目录(默认为 /.garmin-mcp) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user garmin-local -- uvx garmin-local-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"garmin-local": {
"command": "uvx",
"args": [
"garmin-local-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"garmin-local": {
"command": "uvx",
"args": [
"garmin-local-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"garmin-local": {
"type": "stdio",
"command": "uvx",
"args": [
"garmin-local-mcp"
]
}
}
}GARMIN_MCP_DATA_DIR env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 anup-shesh 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 garmin-local-mcp@0.1.9 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/anup-shesh-garmin-local-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.1.9)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Supabase, Neon, Keboola MCP, Dbmcp, Aiven MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
Database MCP server for MySQL, MariaDB, PostgreSQL & SQLite with PII redaction and write-prevention
Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.
| 本项 Garmin Local MCP | Supabase | Neon | Keboola MCP | Dbmcp | Aiven MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 需要安装在电脑上 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 是 | 否 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 5/5 | 5/5 | 3/3 | 3/3 |
| 许可证 | MIT | Apache-2.0 | MIT | MIT | MIT | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever, even when the API is down.
If you don't own a Garmin, or just want to see what the tools return before handing over credentials, seed a synthetic store:
pip install garmin-local-mcp
garmin-local-mcp --data-dir ~/.garmin-mcp-demo demo garmin-local-mcp --data-dir ~/.garmin-mcp-demo serve
That generates 180 days across every table, then serves them over MCP. No login, no network, no account.
The data is generated rather than recorded, but it is not random. A latent recovery factor drives HRV up while resting heart rate goes down, training load raises the *next* day's resting heart rate, a six-day illness window sits in the middle of the range, and a few sleep nights are deliberately missing. Sleep timing carries a planted chronotype (MCTQ MSFsc 03:45, with alarm-pinned work mornings and later, longer free nights), and the sleep score drops with distance from that natural wake time. So the analysis tools have something real to find. Over the full 180 days (exact figures shift a little with the end date, because training days depend on the weekday):
| Ask | Returns |
|---|---|
correlate(hrv, resting_hr) | −0.4 to −0.6, a genuine inverse relationship |
correlate(training_load, resting_hr, scan_lags=True) | near 0 at lag 0, +0.4 to +0.65 at lag 1 (90 to 100 training days, significant after correcting for the 15 lags scanned): the effect is next-day |
anomalies() | the illness window, flagged across resting HR, HRV, skin temperature, sleep score and stress at once |
gaps() | the missing sleep nights |
circadian() | MSFsc within 10 minutes of the planted 03:45, a circadian wake around 07:45, and evidence supportive (the most that two holdout folds allow) |
The analysis tools default to the last 30 days, which misses the illness window, so ask about the whole range (demo prints it). On a short window a lag scan has little to work with; correlate says so in its note when the strongest lag is not significant once all 15 lags are accounted for.
sync_status reports demo_store: true on these stores, so an assistant can never present generated numbers as real measurements. The generator is deterministic — --seed reproduces a store exactly, and --days changes the range. demo refuses to overwrite a database it did not generate.
Most Garmin MCP servers are thin live wrappers around Garmin's unofficial API. Every question your AI assistant asks becomes one or more live API calls returning large raw JSON blobs (a single raw sleep response runs around 230 KB), which makes multi-month questions like "how does my sleep correlate with training load?" expensive to ask.
That design is no longer universal. Since Garmin's auth change in March 2026 broke the ecosystem for several weeks, a number of projects have added local storage, and the largest server computes training-load and HRV trends server-side. Data ownership and server-side analysis are both crowded ground now. Three things are not:
circadian estimates your chronotype from your watch's sleep times (the Munich Chronotype Questionnaire's sleep-debt-corrected mid-sleep) and the wake time that fits it, with an 80% interval on each and a check of how much the answer moves under other reasonable settings. Then it asks whether waking near that time actually went with higher Garmin scores on nights the model never saw, beyond what sleep duration and schedule regularity explain, and says plainly when it didn't. Chronotype on its own is not new: other tools, including at least one MCP server, report MCTQ-style chronotype from wearable sleep data. I have not found another that puts uncertainty on the answer or validates it out of sample. See Sleep timing and chronotype.The rest of the design follows from keeping your own copy:
circadian, the richest, stays under 3 KB), so nothing floods the model's context.| garmin-local-mcp | Most other Garmin MCPs | |
|---|---|---|
| Zero-auth ingest path | Yes (wellness FIT bundle import) | No |
| Lag-aware correlation (-7 to +7 days) | Yes | No |
| Chronotype and wake-time advice, validated on unseen nights | Yes (intervals, stability check, rolling holdout) | A few report chronotype; none found that validate it |
| Response size discipline | Compact columnar tables, typically < 2 KB | Raw payloads; the largest server documents skipping its detail endpoint at 50-500 KB |
| Works offline after an API breakage | Yes, analysis plus FIT ingest | Varies; some keep a local cache |
| Local data store you own | Yes (raw JSON + SQLite) | Several now do this too |
| Tool count | 13 curated | 18 to 148 |
Requires Python 3.12+.
pip install garmin-local-mcp
Or run it without installing, via uv:
uvx garmin-local-mcp --help
1. Log in once (MFA supported; tokens persist locally, so future runs never ask for a password):
garmin-local-mcp login
2. Backfill your history. The sync is resumable, safe to interrupt, and throttled to be polite to Garmin's servers. A year of history is roughly 1,800 requests; for long backfills, start it and let it run (overnight works well). If it gets rate limited or interrupted, re-run the same command and it resumes where it left off.
garmin-local-mcp sync --from 2026-01-01
3. Register the MCP server with your client (see Client setup for Claude Desktop, Cursor, and other clients):
claude mcp add --scope user garmin -- garmin-local-mcp serve
4. Ask questions. Examples of what Claude can now answer from your local warehouse in one or two tool calls:
The server speaks stdio, so any MCP client works. pip install garmin-local-mcp first (or use the uvx variants below, which need nothing installed beyond uv).
Claude Code
claude mcp add --scope user garmin -- garmin-local-mcp serve
Claude Desktop, one-click: download garmin-local-mcp-x.y.z.mcpb from the latest release, then in Claude Desktop open Settings > Extensions > Advanced settings, click "Install Extension…", and select the file. Requires uv on your PATH; the extension installs and runs the server from PyPI via uvx, so no manual Python setup is needed. If the install dialog warns about a missing Python >=3.12, you can ignore it: uv provisions its own interpreter.
Claude Desktop, manual (Settings, then Developer, then Edit Config; add to claude_desktop_config.json):
{
"mcpServers": { "garmin": { "command": "garmin-local-mcp", "args": ["serve"] } } }
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project):
{
"mcpServers": { "garmin": { "command": "garmin-local-mcp", "args": ["serve"] } } }
Any other stdio client / no local install (requires uv):
{
"mcpServers": { "garmin": { "command": "uvx", "args": ["garmin-local-mcp", "serve"] } } }
Note: login and the initial backfill sync are CLI steps (see Quickstart); the MCP server itself never prompts for credentials.
| Tool | What it does |
|---|---|
auth_status | Check whether stored Garmin Connect tokens exist (use before sync, or after an auth error). |
sync | Fetch up to 60 days from Garmin Connect into the local store (default: last 30 days ending yesterday; big backfills belong in the CLI). |
sync_status | Local data coverage per table, last sync time, and pending sync errors. |
get_day | One merged view of a single day: wellness, sleep, HRV, training status, performance scores, activities, and data-quality flags. |
query_metrics | Columnar time series for one or more metrics between two dates, with daily/weekly/monthly aggregation and optional stats. |
correlate | Pearson/Spearman correlation between two metrics, with day-lag support and an optional scan over lags -7..+7. |
baselines | Personal mean +/- sd band per metric over a trailing window (default 28 days), to judge what is normal for this user. |
anomalies | Outlier days (z-score deviations) and sustained streaks (5+ consecutive days on one side of the mean). |
list_activities | Recent activities newest-first as a compact table, filterable by type, date range, and minimum distance. |
get_activity | Full stored summary row for one activity (summary fields only, no GPS or sample streams). |
gaps | Missing days per table plus unresolved sync errors, to find holes worth re-syncing before drawing conclusions. |
import_fit | Zero-auth offline ingest of a manually exported Garmin wellness FIT bundle. |
circadian | Chronotype (MCTQ), sleep need and an inferred wake window, each with an 80% interval, plus out-of-sample evidence on whether that window goes with higher Garmin scores. See Sleep timing and chronotype. |
Only sync and import_fit write anything, and only inside the data directory. The server never prompts: auth problems come back as structured errors with a hint pointing at the login CLI.
Available metric names include resting_hr, sleep_score, hrv, steps, stress_avg, body_battery_high, skin_temp_dev_c, vo2max, fitness_age, achievable_fitness_age, training_load, endurance_score, hill_score, readiness_score, race_5k_s, the sleep-timing metrics sleep_onset_min, wake_time_min and mid_sleep_min (minutes from midnight of the wake date, so a 23:00 bedtime is −60), and about 35 more; any tool given an unknown name returns the full list.
Garmin's periodic fitness scores land in their own performance table: endurance score, hill score (with its endurance and strength sub-scores), training readiness (score, level, recovery time) and race predictions for 5k, 10k, half and full marathon (all in seconds).
These update on Garmin's own cadence rather than daily, so performance is deliberately excluded from gaps — a