> training.insights

> connect mcp://training.insights … ok · 11 tools · 637 activities · 14 races · last run 6d 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 in the quiet stretch after a marathon. He ran the Royal Victoria Marathon on 11 October, covering 42.6km in 5:15:27 — an average of 7:24/km, and a long way outside the 3:50 he had targeted, with his heart rate drifting well upward over the second half in a way it had not in any of his spring races. Since then the running has been short and sparse: nine runs in the last four weeks totalling 86.7km, with the marathon itself making up half of that. The weeks since have been 11.3km, 18.0km and, so far this week, a single 4.4km jog, on gently rolling ground.

So this is easing, not building, and clearly so. Total running in the past month is down by well over half against the month before it, four of the last seven days were rest days, and the body's accumulated workload is now sitting meaningfully below what Steve Gomori had been carrying through the autumn — the pattern of a taper or a post-race lull rather than a build. The runs that remain are varied in length rather than samey, which is the gentler way to come back. Pace on easy running is a touch slower than a month ago, about 10s/km once the hills are accounted for, and the heart-rate drift within runs reads as moderate — unremarkable so soon after 42km.

Nothing is on the race calendar ahead, so there is no target date shaping the next few weeks. The reference points behind him are strong: a 10K in 46:53 in April and three half marathons between 1:42 and 1:45 across February, May and June, all run with very little cardiac drift. Against those, the marathon stands out as the outlier rather than the trend.

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.