GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
MCP server for Garmin Connect IQ developers: store portal, SDK builds, simulator. Read-only default.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CIQ_MCP_ALLOW_WRITES, CIQ_MCP_TOOLSETS, CIQ_MCP_PROFILE, CIQ_MCP_SDK, CIQ_MCP_BROWSER, CIQ_MCP_PORTAL_COOKIES标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
运行前请先填写空着的值。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
CIQ_MCP_ALLOW_WRITES envCIQ_MCP_TOOLSETS envCIQ_MCP_PROFILE envCIQ_MCP_SDK envCIQ_MCP_BROWSER env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 idoo 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CIQ_MCP_PORTAL_COOKIES
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于12天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for Garmin Connect IQ developers. Your agent gets the store (versions, listings, reviews, installs), SDK builds, the simulator and, if you want it, your Garmin Connect data. Read-only by default, and it asks before anything goes public. The binary is connect-iq-mcp.
Paste this into whatever AI is writing your watch face right now:
Set up the connect-iq-mcp server for me: https://github.com/idoo/connect-iq-mcp/blob/main/docs/INSTALL.md
Or by hand, in three steps:
curl -fsSL https://github.com/idoo/connect-iq-mcp/releases/latest/download/install.sh | sh # or: brew install idoo/tap/connect-iq-mcp
connect-iq-mcp auth login # opens Garmin's sign-in page, tick Remember me connect-iq-mcp config install claude-code # or claude-desktop, codex, cursor, vscode, windsurf
Builds and the simulator also need Garmin's SDK Manager and Java 17+. Details, Windows and Linux: docs/INSTALL.md. Sign-in, signing keys, CI, upgrades and fixes: docs/FAQ.md.
You're handing it your Garmin developer account, so here's what you can check yourself instead of taking my word for it:
go install github.com/idoo/connect-iq-mcp/cmd/connect-iq-mcp@latest.apps.garmin.com, Garmin's SSO in the sign-in browser, and Garmin Connect if you turn it on. No telemetry. SECURITY.mdchecksums.txt, and build provenance attestations. The macOS binaries are also signed with my Developer ID and notarized by Apple.govulncheck, and a tag can't ship with a known reachable vulnerability.Check a download with the GitHub CLI:
gh attestation verify connect-iq-mcp_<version>_<os>_<arch>.tar.gz --repo idoo/connect-iq-mcp \
--signer-workflow idoo/connect-iq-mcp/.github/workflows/release.yml --source-ref refs/tags/v
or with cosign:
cosign verify-blob --bundle checksums.txt.sigstore.json \
--certificate-identity 'https://github.com/idoo/connect-iq-mcp/.github/workflows/release.yml@refs/tags/v ' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com checksums.txt shasum -a 256 -c checksums.txt --ignore-missing
On a Mac, spctl -a -vv -t install connect-iq-mcp should say source=Notarized Developer ID.
The .mcpb and tools.json are listed in checksums-extra.txt with their own checksums-extra.txt.sigstore.json. Both checks above work on them the same way.
Garmin has no public store API, so Connect IQ MCP uses the same private endpoints the developer portal website uses, plus Garmin's sign-in. Garmin can change them and break this any day, or object to it. Renewal runs a headless browser that doesn't announce itself as automated, and automated access may be against the portal's terms: it's your account and your call. Request rates stay low.
Not affiliated with or endorsed by Garmin. Garmin, Connect IQ and fēnix are trademarks of Garmin. If Garmin objects to the name, the name changes.
| this one | web portal | monkeyc + manual upload | wroblisko | andreycooper | |
|---|---|---|---|---|---|
| Works from your agent | + | − | − | + | + |
| Store: reviews, installs, listings | + | + | − | − | − |
| Publish a version | + | + | ~ | − | − |
| SDK builds | + | − | + | + | + |
| Simulator screenshots and input | + | − | ~ | + | + |
| Unit tests in the simulator | + | − | + | − | + |
| Prebuilt signed binary | + | − | − |
~ by hand. Screenshots and simulator input are macOS only here and in andreycooper's; wroblisko's also does Windows.
It can't publish anything until you let it. Publishing a version and editing the listing wait for your yes; builds and the simulator don't ask. A 1-star review that says "ignore previous instructions" is still just a 1-star review. More in docs/SAFETY.md. Report holes privately: SECURITY.md.
Tools come in toolsets, so your agent only sees what you use. store, sdk and simulator are on out of the box. connect (your Garmin Connect data, after auth login --connect) and store_experimental (portal calls nobody has tried live yet) are off. Pick with CIQ_MCP_TOOLSETS (all, +connect) or ask the agent mid-chat. Every tool: docs/TOOLS.md.
MIT © Ivan Verevkin