#1 AI CodingUnknown
bosch-flow-mcp — alternative #1 to garmin-local-mcp
🐍 ☁️ 🏠 - MCP server for Bosch eBike Flow (Smart System / BES3). Read-only, signs in with your own Bosch account via PKCE. Battery health and...
GitHub source
Recorded alternatives
Alternatives to garmin-local-mcp
Every candidate below sits in AI Coding. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.
#2 AI CodingUnknown
whoop-mcp-server — alternative #2 to garmin-local-mcp
🐍 🏠 🍎 🪟 🐧 - WHOOP recovery, sleep, strain, and workouts with server-side analysis: trends, lag-aware correlations, training load, and full-h...
GitHub source
#3 AI CodingUnknown
mcp-server-terraform — alternative #3 to garmin-local-mcp
📇 🏠 🍎 🪟 🐧 - Safety-first Terraform operations: plan/apply/destroy with two-step confirmation gates, plan risk & cost analysis that flags exp...
GitHub source
#4 AI CodingUnknown
lean-memory — alternative #4 to garmin-local-mcp
🐍 🏠 🍎 🪟 🐧 - Embedded, local-first agent memory in a single SQLite file per namespace (vec0 + FTS5 hybrid retrieval). ADD-only history querya...
GitHub source
#5 AI CodingUnknown
longhand — alternative #5 to garmin-local-mcp
🐍 🏠 🍎 🪟 🐧 - Persistent local memory for Claude Code. Indexes every session JSONL verbatim into SQLite + ChromaDB for semantic recall (~126ms...
GitHub source
#6 AI CodingUnknown
zotio — alternative #6 to garmin-local-mcp
🏎️ 🏠 ☁️ 🍎 🪟 🐧 - Zotero MCP server (zotio-mcp) with a capability-tagged tool registry and preview-first, journaled writes (an agent can't sil...
GitHub source
#7 AI CodingUnknown
alphafold-sovereign-mcp — alternative #7 to garmin-local-mcp
🐍 🏠 ☁️ 🍎 🪟 🐧 - AlphaFold MCP server integrating AlphaFold DB with eight additional public biomedical data sources, backed by a local SQLite...
GitHub source
#8 AI CodingUnknown
cellar — alternative #8 to garmin-local-mcp
🦀 📇 🏠 🍎 🐧 - Hybrid computer-use runtime. Fuses accessibility tree + Chrome DevTools Protocol + vision into structured context with per-eleme...
GitHub source
Questions about this page
How were these alternatives selected?
Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.
Are these alternatives ranked by payment?
No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.
Always verify current terms with garmin-local-mcp directly — Oryxen records pricing classes, not live quotes.