Kaiord
MCP server for workout-file conversion: convert, validate, and inspect FIT, TCX, ZWO, and Garmin Connect files, with round-trip-safe conversions through the KRD canonical JSON format. Runs locally over stdio via npx -y @kaiord/mcp. Part of the open-source, local-first Kaiord training platform.
README
Kaiord ā Open-Source Health & Fitness Data Framework
kaiord.com | Editor | npm
Kaiord is an open-source framework for creating, converting, and managing health & fitness data.
It provides:
@kaiord/core: a TypeScript library with format adapters for .fit, .tcx, .zwo, and .krd (Kaiord) files, plus Garmin Connect API integration.@kaiord/cli: a command-line tool to convert, validate, and compare files across formats.@kaiord/mcp: an MCP server exposing Kaiord tools to AI agents (Claude Desktop, Claude Code, etc.). Published in the official MCP registry asio.github.pablo-albaladejo/kaiord.- Workout Editor: a web application to create and edit workout files visually.
⨠Features
- Visual Workout Editor - Create and edit workouts in your browser
- Unified JSON-based format
.krd(Kaiord Representation Definition) - Schema validation (Zod)
- Round-trip safe conversions between FIT / TCX / ZWO / GCN / KRD
- Hexagonal architecture & fully typed API
Supported FIT Fields
Workout Metadata
- Sub-sport categorization: Detailed sport types (trail running, indoor cycling, lap swimming, etc.)
- Pool dimensions: Pool length and unit for swimming workouts
Workout Steps
- Coaching notes: Instructional text for each step (max 256 characters)
- Swimming equipment: Fins, kickboard, paddles, pull buoy, snorkel
Duration Types
- Time & distance: Standard interval durations
- Calorie-based: Steps ending after burning specified calories
- Power-based: Steps ending based on power thresholds (watts)
- Heart rate conditionals: Steps ending based on HR thresholds (bpm)
- Repeat conditionals: Repeat blocks until time/distance/calories/HR/power targets reached
Known Limitations
- Training Stress Score (TSS): The
training_peaks_tssduration type is not yet implemented in the FIT converter. This is a TrainingPeaks-specific metric that requires additional mapping logic. Contributions welcome!
š Local-first architecture
Kaiord is local-first: your data lives on your device, because there is no Kaiord server to send it to. There are no accounts and no backend.
- Storage is your browser's IndexedDB. The Workout Editor persists every workout, template, profile, and setting in a local Dexie.js / IndexedDB database (
new KaiordDatabase()indexie-database.ts), and the UI reads it reactively throughuseLiveQuery. Nothing is written to a remote database ā see the "Persisted data ā Dexie" rule in State Management. - Conversions run entirely on your machine. FIT / TCX / ZWO / GCN ā KRD conversion happens in-process ā client-side in the editor (
import-workout-formats.ts,export-workout-formats.ts) or locally in the@kaiord/cli. Files never leave your device to be converted. - Sync is opt-in and goes to your cloud. Data leaves the device only if you connect Google Drive. The cloud-sync adapter uses the Google Identity Services
drive.appdatascope, so synced data lands in your own Drive's app folder; the access token lives only in memory for the session and is never persisted by Kaiord. - Integrations use your logged-in session ā no credential proxy. Garmin, WHOOP, and Train2Go connect through browser-extension "bridges" (
garmin-bridge,whoop-bridge,train2go-bridge) that piggyback on your existing browser session. Peropenspec/specs/adapter-contracts/spec.md, a bridge "SHALL NOT store, transmit, or manage user credentials"; authentication is "delegated entirely to the browser's cookie jar." No third-party server proxies your credentials or your data. - Works offline. Because all logic and storage are client-side, the editor keeps working with no network connection once loaded.
š Documentation
Comprehensive documentation is available in the /docs directory:
- Getting Started - Installation, basic usage, and quick examples for both library and CLI
- Architecture - Hexagonal architecture, ports & adapters pattern, and design principles
- Testing - Testing strategy, TDD workflow, and coverage requirements
- Deployment - CI/CD pipeline, GitHub Pages deployment, and npm publishing
- Contributing - Contribution guidelines, development workflow, and code standards
- KRD Format - Complete specification of the Kaiord Representation Definition format
- AI Agents - Guidance for AI-assisted development
š§© Tech Stack
| Layer | Tooling |
|---|---|
| Core | TypeScript, tsup, Zod |
| CLI | yargs |
| Web App | React, Zustand, Tailwind, Radix UI |
| Testing | Vitest, Playwright |
| Package manager | pnpm |
š Monorepo Layout
kaiord/
āā packages/
ā āā core/ ā domain types, schemas, ports & use cases
ā āā fit/ ā Garmin FIT format adapter
ā āā tcx/ ā Training Center XML adapter
ā āā zwo/ ā Zwift ZWO format adapter
ā āā garmin/ ā Garmin Connect API adapter
ā āā cli/ ā command-line interface
ā āā mcp/ ā MCP server for AI/LLM integration
ā āā workout-spa-editor/ ā web application (https://kaiord.com/editor/)
āā docs/ ā documentation
āā LICENSE
āā README.md
āā pnpm-workspace.yaml
š Quick Start
Try the Web App
Create and edit workouts visually in your browser. No installation required.
Use the Library
pnpm install
pnpm -r build
pnpm -r test
# Example usage
pnpm kaiord --help
For detailed installation instructions and usage examples, see the Getting Started Guide.
š CI/CD Pipeline
Kaiord uses GitHub Actions for continuous integration and deployment:
- Automated Testing: Multi-version testing on Node.js 22.x (Maintenance LTS) and 24.x (Active LTS)
- Code Quality: ESLint, Prettier, and TypeScript strict mode validation
- Release Automation: Changesets for version management and npm publishing
- Security: Weekly dependency vulnerability audits, CodeQL static analysis, and automated dependency updates
For complete CI/CD documentation, deployment guides, and npm publishing instructions, see Deployment.
Mechanical invariant guards
Beyond linting, the repo enforces its architecture and conventions with 60+ purpose-built guard scripts under scripts/, each with its own co-located test suite. They run on every commit (husky pre-commit) and in CI (pnpm test:scripts), and cover, among others:
- Hexagonal architecture ā layer purity, adapter isolation, and the
packages/core/src/directory allowlist (check-architecture.mjs) - Package dependency graph ā every
@kaiord/*dependency must match the spec table (check-package-deps.mjs) - Test conventions ā
should-prefixed titles and Arrange/Act/Assert structure on every test (check-test-title-should.mjs,check-test-aaa.mjs) - Privacy ā no runtime values interpolated into toasts or console logs (
check-no-pii-leakage.mjs) - State discipline ā no Zustand store writes persistence directly (
check-no-zustand-writethrough.mjs) - Spec hygiene ā OpenSpec format, archive dates, and auto-generated indexes stay in sync (
check-spec-format.mjs,check-archive-*.mjs)
If a rule matters here, a script enforces it ā documentation describes the rules, but the guards are what make them true.
Contributing
To contribute to Kaiord:
- Fork and clone the repository
- Create a feature branch:
git checkout -b feature/my-feature - Make your changes following the code style guidelines
- Add a changeset:
pnpm exec changeset(for version-worthy changes) - Test locally:
pnpm -r testandpnpm -r build - Submit a PR: All checks must pass before merging
For detailed contribution guidelines, development workflow, and code standards, see Contributing.
š References & Resources
Format Specifications
- Garmin FIT SDK (JavaScript) - Official FIT protocol implementation
- FIT Workout Files Cookbook - Guide to encoding workout files
- FIT File Types: Workout - Workout file type specification
- Training Center XML (TCX) - Garmin's XML-based format
- TCX Schema (XSD) - Official Garmin TCX schema definition
- Zwift Workout Format (ZWO) - Zwift's XML-based workout format
ā¤ļø Support
If you find Kaiord useful, consider supporting its development:
- ā Star this repo to help others discover it
- š Sponsor on GitHub
- ā Buy me a coffee
Your support helps maintain and improve Kaiord for the fitness community!
š License
MIT Ā© 2025 Pablo Albaladejo See LICENSE for details.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.