Listed from the MCP registry; nobody on Odel publishes it.
Summarize local build and cache footprint using size and age buckets without returning paths or...
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y build-cache-mcp
MCP client config
{
"mcpServers": {
"build-cache": {
"command": "npx",
"args": [
"-y",
"build-cache-mcp"
]
}
}
}Build Cache summarizes local build and cache footprint. It helps explain why a workspace is slow or large without exposing filenames or contents.
npm install
npm test
npm start
Use inspect_build_cache with a local project path.
Only file metadata inside recognized artifact directories is read. The response contains aggregate size and age buckets, directory counts, and file counts. It does not return paths, names, contents, or dependency data. Recursion, file count, file size, and total byte limits prevent unbounded scans.