v1.0.0b2

What's Changed

• Add glama.json for the Glama directory listing by @futureweb in #33
• Report the package version in serverInfo by @futureweb in #34
• README: mcpservers.org listing badge by @futureweb in #35
• Lap-press steps: write until_lap_press as Intervals.icu's Press lap marker by @futureweb in #36
• README: route-aware lap-press workouts, status and highlights by @futureweb in #37
• Lap-press steps confirmed on a Garmin Edge 1040 by @futureweb in #38
• Coaching protocol P1: read fresh, free text as data, health markers, date anchors, n/a in intervals by @futureweb in #39
• Review follow-ups for 1.0.0b2: lap-press steps open in the execution analysis, health note window, event last day, display rounding by @futureweb in #40
• Release 1.0.0b2 by @futureweb in #41

Full Changelog: v1.0.0b1...v1.0.0b2

v1.0.0b1

What's Changed

• Phase 3: analytics quality, bug fixes and compact outputs by @futureweb in #6
• OAuth: sign in with Intervals.icu, permission scopes, CIMD + private_key_jwt, RFC 9207, /mcp + /sse by @futureweb in #3
• Phase 2: performance analytics, execution analysis, detail levels, OAuth server and CI fixes by @futureweb in #2
• Futureweb Intervals MCP 1.0.0b1: coaching tools, analytics, OAuth by @futureweb in #1
• Security updates: MCP SDK 1.30, Starlette 1.7 and more; allowlist for public Host headers by @futureweb in #12
• Partial event/note updates, event category, absolute pace targets by @futureweb in #13
• Tool annotations from the permission class by @futureweb in #14
• Training load, intensity distribution, durability and load projection tools (after #150 by morritter) by @futureweb in #15
• Phase 5: polish from the coach's live test (also fixes upstream #134, #132) by @futureweb in #16
• Sign-in with the Intervals.icu API key and optional TOTP second factor by @futureweb in #17
• Do not retry POST requests on server errors by @futureweb in #18
• Security: confine identifiers to their path segment, scrub secrets, keep the shared client open across sessions by @futureweb in #19
• Keep permission scopes on refresh, bound dynamic registration and log values by @futureweb in #23
• Security and operations review fixes (SEC-4..SEC-13, OPS-2..OPS-19) by @futureweb in #24
• Phase 6 (B3): what-if plan simulation, target-day form and plan checks in get_load_projection by @futureweb in #20
• Add long-ride fatigue profile, submax test trends and multi-ride power meter comparison by @futureweb in #21
• Phase 6 B2: data audit, fueling analysis, W′, weather and same-route history by @futureweb in #22
• Fix analytics review findings: plan alignment across auto-laps, drift sign, zones, wellness zeros by @futureweb in #26
• Fix review findings: safe write tools, validated workouts, API client errors, limits and time zone by @futureweb in #25
• Flag today's incomplete wellness record in wellness, recovery and coach tools by @futureweb in #27
• Stage 3A: compact tool catalogue (42k -> 22.6k tokens), tool sets, guides, prompts, follow-ups by @futureweb in #28
• Stage 3B: write safety (dry runs, duplicate check, read-back, delete echo) and six fixes from #28 by @futureweb in #29
• Optional multi-user mode: per-connection Intervals.icu credentials (MCP_TENANCY=multi) by @futureweb in #30
• Prepare publishing: PyPI trusted publishing, Docker Hub, MCP Registry, Claude Desktop bundle by @futureweb in #31
• Release 1.0.0b1 by @futureweb in #32

New Contributors

• @futureweb made their first contribution in #6

Full Changelog: https://github.com/futureweb/intervals-mcp-server/commits/v1.0.0b1