v0.12.0 — run/walk-aware stream analytics, gear tracking, CI estimation

[0.12.0] — 2026-06-11

Breaking Changes

• Removed include_legacy param from get_weekly_summary and get_current_pmc.
  The lbss_legacy key is no longer emitted in tool output.
  To compare against an older or alternative LBSS field ad-hoc, pass lbss_field per-call
  (e.g. lbss_field: "StrydLBSSmod").
• Removed LBSS_FIELD_LEGACY env var. The server no longer reads this variable;
  any existing .env entry is silently ignored (Zod unknown-key strip).
  Remove the line from your .env and MCPB user_config if present.

New Features

• avg_stride_length_m per split and overall in get_activity_streams_summary.
  Derived as velocity / (cadence_stream × 2 / 60); uses the run cadence stream (rpm,
  one-foot), verified against Intervals.icu average_cadence.

• EXTRA_STREAM_FIELDS env var — comma-separated Intervals custom stream codes
  (e.g. StrydLSS,StrydTemp,StrydHumidity) fetched and surfaced as extras per split
  and overall in get_activity_streams_summary. Requires custom stream mapping on an
  Intervals.icu activity page (CHARTS → CUSTOM STREAMS → ADD STREAM). Backward-compatible:
  extras key is absent when not configured.

• run_fraction + extras_run in get_activity_streams_summary.
  run_fraction: share of valid samples at or above the run-gate cadence threshold
  (default 70 rpm = 140 spm), per split and overall.
  extras_run: extras averages restricted to running samples only, for separating
  per-stride metric change from walk-mix dilution (e.g. StrydLSS stiffness drift vs.
  gait-mix change in ultra-distance races).
  Configurable via run_gate_cadence_rpm param (range 40–120).
  Both keys absent when cadence stream is not present (backward-compatible).

• run_gate_cadence_rpm param in get_activity_streams_summary (default 70,
  range 40–120). Echoed in data_quality.run_gate_cadence_rpm.

Internal

• LBSS_FIELD_LEGACY / lbssFieldLegacy removed from config, tool registry, and
  MCPB manifest.json user_config.
• .env.example reorganized into Activity custom fields and Streams sections.
• manifest.json user_config: removed lbss_field_legacy, added extra_stream_fields.

---

MCPB Bundle

SHA-256: 6f56e25b7d17c5db3c9ba19a321339b4395e2049b8b2dfce7ed8ca7b31c96dc2

Verify with:

shasum -a 256 Intervals-MCP-Server-with-STRYD.mcpb

v0.6.0 — configurable LBSS/ILR field names + include_legacy

Highlights

• LBSS / ILR custom-field names are now configurable (LBSS_FIELD / LBSS_FIELD_LEGACY / ILR_FIELD, plus a per-call lbss_field override on the aggregation tools) — a recalibrated or renamed field needs no code change.
• get_weekly_summary / get_current_pmc gain include_legacy to report the legacy LBSS field side by side for migration checks.

⚠️ Breaking default change

The default LBSS field moved StrydLBSSmod → StrydLBSSv2 (a Stryd-faithful recalibration).

• If your account only has the community StrydLBSSmod field, either build StrydLBSSv2 from the field recipes, or restore the previous behavior with LBSS_FIELD=StrydLBSSmod.
• Field recipes: https://github.com/methylone/Intervals-MCP-Server-with-STRYD/wiki/LLM-Agent-Recipes

Install

• npm: npx -y intervals-mcp-with-stryd@0.6.0
• MCPB bundle (Claude Desktop): download Intervals-MCP-Server-with-STRYD.mcpb below.

Bundle verification

SHA-256 (Intervals-MCP-Server-with-STRYD.mcpb):
1aad26c0e4f4e922cb88573d4b15b1122a80711191dddc9d5e13516372d17abd
Verify per SECURITY.md before installing.

v0.5.0

v0.5.0

Read-only mode and version single-source-of-truth.

• Read-only mode (READ_ONLY=true): withholds the four account-writing tools (create_events / update_event / delete_event / delete_events). Local-only tools (clear_cache / set_cache_enabled) stay available. Applied identically to the MCP server and the CLI via a single getActiveTools() filter so the two surfaces can't diverge.
• Version single-source-of-truth: serverInfo.version now reads package.json at runtime (src/version.ts), ending the hard-coded "0.1.0" drift.
• MCPB user_config: new read_only and cache_enabled toggles; the api_key field now links to SECURITY.md.
• Secret-scan guard: opt-in .githooks/pre-push runs gitleaks (default ruleset) on the commits being pushed. Enable with git config core.hooksPath .githooks.
• PII config externalized to pii-guard.config.json (allowlists for placeholder home paths and RFC 2606 example domains).

Verification

• npm test: passed (194 tests)
• npm run build: passed
• npm run mcpb:pack (prod-only node_modules): passed
• node scripts/check-mcpb-pii.mjs intervals-mcp-with-stryd.mcpb: passed — 0 findings (structural + deny-list deep check)

SHA-256

Verify the downloaded bundle (see SECURITY.md):

ddc74dfb99bef7f24e3d89dd96a1940a7e138ebb8400e9c12e805cd80fec3d6f  intervals-mcp-with-stryd.mcpb

v0.4.0

v0.4.0

Public PII safeguard refinement release.

• Refined repository PII checkers to reduce documented false positives.
• Added explicit allowlists for RFC 2606 example email domains and placeholder home paths using username you.
• Kept npm tarball and MCPB release gates green.

Verification

• npm run build: passed
• npx @anthropic-ai/mcpb pack . intervals-mcp-with-stryd.mcpb: passed
• node scripts/check-mcpb-pii.mjs intervals-mcp-with-stryd.mcpb: passed, 0 findings in structural checks

SHA-256

29422fda16237a7529719ebccd3ff66f7c8c501e067bc1f40cdf767b625edb2a intervals-mcp-with-stryd.mcpb

v0.1.0 — Initial public release

First public (AGPL-3.0) release of the Intervals.icu MCP Server.

A local Model Context Protocol server that gives an AI client (Claude Desktop, Codex, etc.) structured access to your Intervals.icu training data, plus deterministic server-side computations (PMC, cardiac decoupling, derived nutrition fields).

Highlights

• Core tools: activities, wellness, events (read + create/update/delete), athlete summaries, stream-level split/decoupling/pacing analysis.
• Stryd extension: a second Performance Management Chart computed server-side from a lower-body load metric (LBSS) via EMA, alongside Intervals.icu's RSS-based PMC; weekly and phase-level load trends.
• stdio and Streamable HTTP transports.
• Disk-backed stream cache (immutable activity streams; runtime on/off + clear tools).

Requirements: Node.js >= 20.12, an Intervals.icu account and API key. See INSTALL.md.