Build Cache Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 30, 2026

Summarize local build and cache footprint using size and age buckets without returning paths or...

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that summarizes a project's build and cache footprint as aggregate size and age buckets, without exposing paths or file contents.

What you can do
  • Inspect a local project's build and cache footprint by passing a project path.
  • Get aggregate size and age buckets, directory counts and file counts for recognized artifact directories.
  • Explain why a workspace is slow or large without receiving filenames, paths, contents or dependency data.
When to use it
Useful when you want an assistant to reason about disk usage or slowness caused by build artifacts and caches in a local project, while keeping file names and contents private.
Requirements
Runs as a local stdio process installed from the npm package build-cache-mcp (Node.js toolchain; the README shows npm install, npm test, npm start). No authentication, environment variables or headers are declared. Desktop only.
Before you install
It reads file metadata inside recognized artifact directories on your machine, though responses are limited to aggregates. Recursion, file count, file size and total byte limits cap scans. No credentials are requested.

Installation

In SourceWeft

  1. Open Build Cache Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

Quick start

bash
npm installnpm testnpm start

Use inspect_build_cache with a local project path.

Privacy and limits

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.

Source: README.md at commit ac0f221

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.