MCP Runbook is a working notebook on the Model Context Protocol and how it connects AI assistants to real endurance training data. No theory. Just setups that actually work.
It is intentionally small. No tracking, no newsletter pop-ups, no infinite-scroll. Articles get written when there is something worth writing about.
Who writes this
I am Felix Benjamin. I run, I ride, and I build software for people who train.
I have been an ambitious runner since 2014 and added road and gravel cycling in 2021. A few highlights along the way: a fast half marathon through the Alstertal in Hamburg in 2019, and the Hamburg Marathon on April 23, 2023.
What I love most are long endurance runs of 30 km and beyond, ideally in the Harburger Berge, the Fischbeker Heide, or the Lüneburger Heide. Most of the experiments on this site come straight out of my own training. I want AI assistants to actually be useful for the analysis and planning a runner does week to week, not just plausible-sounding text.
Tredict
I am the founder and developer of Tredict, an endurance training platform I have been building since 2019. Tredict can expose its data through an MCP server, which is why most posts on this site use Tredict as the example platform.
This site is editorially independent in form, but the affiliation is real and worth stating up front. When I write that a workflow works well with Tredict, that is both a genuine observation and the perspective of someone who built the thing. I try to be honest about limits and failure modes.
What you'll find here
- Practical MCP workflows for endurance sports that hold up in real training
- Honest write-ups of what worked, what didn't, and why
- Setup notes for connecting AI assistants to training data
Contact
Email: felix@mcprunbook.com
For new posts, the RSS feed is the canonical way to follow along.