garmin-documentation
MCP server for Garmin Connect IQ API documentation - complete offline access to SDK 8.2.3
claude mcp add --transport stdio ztuskes-garmin-documentation-mcp-server node /path/to/garmin-documentation-mcp-server/dist/index.js \ --env NODE_ENV="production" \ --env LOG_LEVEL="info" \ --env GARMIN_DOCS_PATH="docs/"
How to use
This MCP server provides offline access to the Garmin Connect IQ 8.2.3 documentation. It exposes a set of Core API tools for searching, inspecting modules and classes, listing modules, and retrieving code examples, along with New Documentation Tools for device references, programming guides, and FAQs. With this server, you can perform semantic searches, drill into module or class details with corrected version context, view programming guides, and quickly locate device-specific capabilities such as memory limits and round-device support. Once running, you can query Claude-based clients to discover API coverage, examples, and troubleshooting resources without needing internet access.
How to install
Prerequisites:
- Node.js (recommended LTS version)
- Access to the Garmin Connect IQ documentation set (8.2.3) to place under docs/ at the project root
Steps:
- Clone or download this repository
- Copy the Garmin Connect IQ SDK 8.2.3 documentation into a docs/ folder at the project root
- Install dependencies:
npm install
- Build the project:
npm run build
- Run the server (production):
npm start
- Optional: run in development mode:
npm run dev
Note: On first run the server will index all documentation files. This may take a few seconds; subsequent runs are faster.
Additional notes
Tips:
- Ensure the docs/ folder is populated with the 8.2.3 documentation before starting the server for proper indexing.
- The Claude integration examples assume the server is accessible at the configured path; update the path in Claude config accordingly.
- Environment variables can influence behavior: GARMIN_DOCS_PATH defines where docs are read from, LOG_LEVEL controls verbosity.
- If you see version mapping issues, verify you are using the v1.0.1-enabled server build which fixed API Level to SDK version mapping.
- For production deployments, consider setting a persistent process manager (e.g., PM2) and configuring proper restart behavior on crashes.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud