What it does
buildtime takes a set of CI runs, each with per-step durations and optional cache-hit flags, and returns a profile. For every distinct step name it gives the number of runs containing the step, its total, average and maximum duration, and its share of the grand total, ranked slowest first. It also names the slowest step, splits the runs into first and second halves to show the percentage change in average run total, compares average run totals for runs with and without a cache hit, and lists steps whose average meets an optional slow threshold.
It suits cases where builds are getting slower and the cause is unclear, or where you want to check whether cache hits are linked to shorter runs. It is exposed as an analyze_build_times tool for MCP clients and as a command-line program that reads a runs JSON file and prints the profile as JSON. The computation is local, with no network access and no configuration, and it reads only the runs you pass in. Results are rounded to four decimal places.
Limitations and requirements
At least one run is required, and each step must include a duration_seconds value. Negative durations and a negative slow threshold are rejected. A missing run or any other invalid input causes an error, and no partial profile is produced. The trend is null with fewer than two runs, and its percentage delta is null when the first half averages zero.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/buildtime
Build bottleneck profiler: slowest steps, run trend, and cache correlation across CI runs.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it