M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGarmin MCP ServerMCP server for accessing Garmin data, with 110+ tools covering fitness, health, and training analytics.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS72 / 100 · B75 / 100 · B
Reliability11 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance16 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Garmin users wanting to centralize fitness data in AI assistants
  • Runners or cyclists needing automated workout generation and scheduling
  • Analytical users who prefer natural language queries for health trends
  • Developers and hobbyists integrating Garmin data into custom toolchains
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Non-Garmin users or those without a Garmin account
  • Applications requiring real-time GPS tracking or instant data push
  • Users who want to bypass authentication (requires Garmin account and OAuth tokens)
  • Destructive operations like deleting activities (not implemented for safety)
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read and edit Garmin Connect data (activities, health metrics, workouts, etc.)
  • Download activity files to local directory
  • Create and schedule workout plans
  • Access user's health metrics and body composition data
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Stores OAuth tokens which expire after ~6 months, requiring re-authentication
  • HTTP transport has no authentication; if exposed on public network, place behind a reverse proxy
  • Some destructive operations (e.g., delete activity) are intentionally not implemented to avoid accidents
  • Many tools may increase LLM context overhead, but can be filtered via environment variables
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, Codex, OpenCodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011