TriathlonPlan

TriathlonPlan — connector documentation

• MCP endpoint: https://triathlonplan.connectorbay.com/mcp
• REST API: POST https://triathlonplan.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://triathlonplan.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://triathlonplan.connectorbay.com/health · Tool schemas: https://triathlonplan.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/triathlonplan · agent@connectorbay.com

About TriathlonPlan

TriathlonPlan is a triathlon training-plan toolkit: four tools, all computed locally with no upstream calls, no accounts and no tracking.

• Training plan builds a real week-by-week plan from a race distance and weeks available, using base/build/peak/taper periodization: weekly hours ramp toward a peak (with a recovery cutback every 4th week), hold at peak with brick workouts, then taper before race day — split into swim, bike, run and brick hours with distance-specific percentages (longer races skew more bike-heavy).
• Brick workout guide explains why bike-to-run "brick" workouts matter and gives example structures by training phase.
• Taper guide gives taper length and weekly volume percentages by race distance, and what to expect.
• Race distances reference lists the standard swim/bike/run distances for sprint, olympic, 70.3 and full-distance triathlons.

This is general training information based on commonly used periodization principles, not personalized coaching or medical advice — if you have a health condition or are new to endurance training, check with a doctor before starting a new plan.

Built and maintained by Unify Dynamics LLC. Contact: agent@connectorbay.com.

Tools

Plan

training_plan — A week-by-week triathlon training plan: swim/bike/run/brick hours per week using base/build/peak/taper periodization, scaled to race distance and experience. Use for "16-week sprint plan for a beginner" or "build me a 70.3 plan, intermediate, 12 weeks". Args: race_distance, weeks_available, experience_level, current_weekly_hours.

Bricks

brick_workout_guide — Why bike-to-run brick workouts matter, and example brick structures by training phase. Use for "why do brick workouts matter". Args: race_distance, phase.

Taper

taper_guide — Taper length and weekly volume percentages by race distance, and what to expect during taper. Use for "how long should my taper be for a full". Args: race_distance.

Reference

race_distances_reference — Standard swim/bike/run distances for sprint, olympic, 70.3 and full-distance triathlons. Use for "what's the swim/bike/run distance for an Olympic triathlon". Args: none.

Conventions

• Read-only. Every tool computes from bundled constants; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input).
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/triathlonplan/support

TriathlonPlan — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What TriathlonPlan is. TriathlonPlan is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for triathlon training-plan generation: a week-by-week plan, brick-workout guidance, taper guidance, and race-distance reference. You interact with your assistant; the assistant sends us only the values needed for that one calculation.

What we receive. The arguments of each tool call — a race distance, weeks available, experience level and optionally your current weekly training hours, or a phase/distance name for reference lookups — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is computed on our server and nothing is stored. All reference constants (peak-hours tables, discipline splits, taper factors, race distances) are hand-curated and bundled with the server; no request is forwarded to any third party, and no query is logged in request bodies, recorded, or used to train anything. Each call is answered independently and nothing carries over between requests.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, or account credentials. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — every tool is computed locally. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. TriathlonPlan is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

TriathlonPlan — Terms of Service

Effective 28 September 2026. These terms govern use of the TriathlonPlan connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. TriathlonPlan returns triathlon training-plan generation — a week-by-week swim/bike/run/ brick plan, brick-workout guidance, taper guidance, and race-distance reference — computed from hand-curated planning defaults and documented periodization principles bundled with the server. It is accessed through an AI assistant or directly over MCP or HTTP.
2. General training information, not coaching or medical advice. TriathlonPlan's plans are general planning information based on commonly used periodization principles, not an individualized training program from a coach or a medical evaluation. Endurance training, especially at longer distances, carries real physical demands; if you're new to it or have a health condition, talk to a doctor before starting a new training plan.
3. Estimates, not prescriptions. Peak-hours tables, discipline splits and taper factors are simplified planning heuristics, not an individualized assessment of your fitness, recovery capacity or injury risk. Adjust or stop based on how your body actually responds.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered on our server and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or training outcome arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/triathlonplan

TriathlonPlan support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://triathlonplan.connectorbay.com/mcp
• REST API: https://triathlonplan.connectorbay.com/openapi.json
• Live status: https://triathlonplan.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. TriathlonPlan never asks for them.