Tyme Wear MCP Server

A Model Context Protocol server that connects Claude to the Tyme Wear breathing sensor platform. Analyze your ventilatory data, activities, thresholds, and training zones directly through Claude.

Built on the same architecture as trainingpeaks-mcp.

What is Tyme Wear?

Tyme Wear makes the VitalPro chest strap, a wearable breathing sensor that measures ventilatory metrics (breathing rate, tidal volume, minute ventilation) alongside heart rate. It uses ventilatory thresholds (VT1, VT2) to define personalized training zones. Used by Team Visma | Lease a Bike.

Related MCP server: XERT Cycling Training

Features

• 20 MCP tools for profile, activities, breathing data, VE thresholds, zone distributions, max values, and exports

• Secure credential storage via system keyring (macOS Keychain / Windows Credential Manager) with AES-256-GCM encrypted file fallback

• Auto-authentication with token caching and automatic re-auth on expiry

• Smart breathing data with summary, window, and full modes to avoid context overflow

Quick Start

1. Install

git clone https://github.com/tkelkermans/tymewear-mcp.git
cd tymewear-mcp
python -m venv .venv
source .venv/bin/activate
pip install -e .

2. Authenticate

tymewear-mcp auth

Enter your Tyme Wear email and password. Credentials are stored securely in your system keyring with an encrypted file fallback.

3. Configure Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "tymewear": {
      "command": "/path/to/tymewear-mcp/.venv/bin/tymewear-mcp",
      "args": ["serve"]
    }
  }
}

Or run tymewear-mcp config to generate the snippet with the correct path.

4. Restart Claude Desktop

The Tyme Wear tools will appear in Claude's tool list.

CLI Commands

Available Tools

Auth & Profile

Activities

Breathing Data

Thresholds & Zones

Max Values

Exports

Example Prompts

Once configured, you can ask Claude things like:

• "Show me my last 10 bike activities"

• "Analyze the breathing data from my ride yesterday — what were my average VE and time in each zone?"

• "What are my current VT1 and VT2 thresholds for cycling?"

• "Export my last activity as a FIT file"

• "Compare my VE targets between running and cycling"

Security

• Credentials stored in system keyring (preferred) or AES-256-GCM encrypted file with PBKDF2 key derivation (600K iterations, machine-specific salt)

• Tokens and credentials are never returned in MCP tool results (sanitized before reaching Claude)

• Environment variable auth available for CI/containers: TYMEWEAR_EMAIL + TYMEWEAR_PASSWORD

• File permissions set to 600 (owner read/write only) on encrypted credential files

Architecture

tymewear-mcp/
├── src/tymewear_mcp/
│   ├── cli.py              # CLI entry point
│   ├── server.py           # MCP server + 20 tool registrations
│   ├── auth/               # Credential storage (keyring → encrypted → env)
│   ├── client/             # Async HTTP client + Pydantic models
│   └── tools/              # Tool implementations
└── tests/                  # 53 tests

Tech stack: Python 3.10+, MCP SDK, httpx, Pydantic, keyring, cryptography

Development

pip install -e ".[dev]"
pytest tests/ -v          # Run tests
ruff check src/           # Lint
mypy src/                 # Type check

License

MIT