> training.insights

> connect mcp://training.insights ok · 11 tools · 618 activities · 13 races · last run 2d ago

Steve Gomori's training data, as analytical tools

Every run is reduced to the metrics that describe an endurance athlete's training and exposed through the Model Context Protocol. Any MCP-compatible AI client can connect and ask about it — including the one answering below.

I'll pull the recent training picture.

Steve Gomori is four weeks out from the Royal Victoria Marathon on Sunday 11 October, and the training reflects it. Over the last 28 days he has run 16 times for 193.6km — roughly four runs a week, averaging 12.1km each, at about 6:14/km across everything from easy jogs to harder structured sessions. The ground is gently rolling rather than flat, which costs him a little under eight seconds a kilometre and means the raw pace understates the work.

The shape is a build that has crested and started to come down. Volume climbed steadily through August to a peak week of 61.3km in the last week of the month, topped by a 25km long run, and the two weeks since have settled back to around 35km each. His seven-day workload now sits well below what his body has grown used to over the past months — the pattern of a taper rather than a slump, with four rest days in the last week. The weeks themselves have been varied rather than samey, which is the easier kind of load to absorb.

One signal worth naming: on longer efforts his heart rate drifts upward relative to his speed more than it ideally would, in the significant range over the last month, and that drift has edged up rather than down through the block. Set against past years, this buildup carries more average weekly distance than the one before his 2025 Victoria marathon (5:47/km there) but a shorter longest run — 25km against 30km, about 59% of race distance where marathon programmes conventionally reach further. His goal pace this time is 5:27/km, and a good share of recent running has landed near it.

Answers come from the same tools any MCP client can call. Each question is answered on its own.

Connect your own client

The server speaks Streamable HTTP and authenticates with a bearer token. Point any MCP client at the endpoint below and it will discover the available tools on connect.

https://training.stevegomori.ca/mcp

Keys are issued on request and are read-only — a client can query the training history and nothing else. Running your own instance needs no key from anyone: the project is self-hostable end to end, against your own exports.