ConnectIQ MCP Server
Pull Garmin Connect IQ SDK documentation and resources into your agent while building watch faces, widgets, or device apps.
Overview
connect-iq-mcp is a Build-phase MCP server that exposes Garmin Connect IQ SDK documentation and resources to coding agents via stdio.
What is this MCP server?
- MCP server focused on Garmin Connect IQ SDK documentation and resources
- npm package connectiq-mcp-server v1.2.0 stdio transport
- Reduces context switching between IDE and scattered SDK web pages
- Targets Connect IQ developers building apps for Garmin devices
- Open-source server on GitHub deugene/connect-iq-mcp
- npm package connectiq-mcp-server version 1.2.0
- stdio MCP transport
- Repository: github.com/deugene/connect-iq-mcp
What problem does it solve?
Connect IQ development stalls when you constantly leave the IDE to hunt SDK docs across Garmin’s scattered reference pages.
Who is it for?
Solo builders shipping Garmin watch apps or widgets who want doc-aware agent help without manual SDK site digging.
Skip if: Non-Garmin mobile apps, pure fitness content businesses, or teams that do not use the Connect IQ SDK at all.
What do I get? / Deliverables
Your agent can answer SDK and platform questions in-context while you write Monkey C and configure Connect IQ projects.
- In-session SDK documentation retrieval for Connect IQ
- Faster agent answers on Garmin API and platform resources
- stdio MCP registration for connectiq-mcp-server 1.2.0
Recommended MCP Servers
Journey fit
How it compares
Connect IQ SDK documentation MCP, not a generic React Native or Apple Watch skill.
Common Questions / FAQ
Who is connect-iq-mcp for?
Garmin Connect IQ developers using AI assistants who need SDK documentation and resources reachable as MCP tools during implementation.
When should I use connect-iq-mcp?
Use it during Build while coding Monkey C, debugging manifest or permission issues, or learning device-specific Connect IQ APIs.
How do I add connect-iq-mcp to my agent?
Install connectiq-mcp-server from npm, add a stdio MCP entry in Claude Code or Cursor pointing at that package, restart the client, and query SDK docs through the server tools.