Ermöglicht es einem AI-Client, die Festplattennutzung von Entwicklern zu scannen und sicher alte Package-Caches, Docker-Images und ungenutzte node_modules zu entfernen.
Auch bekannt als roystondwork-dev/diskdiet
- Stars
- 1
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.7.1
- Letzter Commit
- 15. Nov. 2026
- Lizenz
- MIT
Was ist diskdiet MCP?
diskdiet ist ein MCP server. Ermöglicht es einem AI-Client, die Festplattennutzung von Entwicklern zu scannen und sicher alte Package-Caches, Docker-Images und ungenutzte node_modules zu entfernen.
Zusammenfassung generiert aus dem README des Projekts
Über diskdiet MCP server
diskdiet ermöglicht es Engineers auf macOS, Linux oder Windows, Speicherplatz in überladenen Entwicklerumgebungen zurückzugewinnen. Durch die Verbindung dieses MCP server mit AI-Clients wie Claude Code, Cursor oder VS Code Copilot kannst du einen Assistenten direkt in deinen Workflow einbinden, um "no space left on device"-Fehler zu diagnostizieren und zu beheben. Der Server bietet Tools, um dein System nach hohen Speicherverbrauch zu scannen und unnötige Dateien sicher zu entfernen, ohne aktive Projekte zu beschädigen.
Er unterstützt eine breite Palette von Developer-Tools, darunter npm, Yarn, pnpm, Bun, pip, uv, Cargo, Go, Gradle, Maven, Playwright, Cypress, Xcode und Docker. Im Gegensatz zu generischen Cleanern nutzt er intelligente Logik, um Dateien zu identifizieren, auf die seit Langem nicht mehr zugegriffen wurde (standardmäßig alles, was seit 30 Tagen unverändert ist). Er kann gezielt ungenutzte Docker-Images, alte Package-Caches oder vergessene node_modules und Zielordner ansteuern, während er sicherstellt, dass aktive Installationen oder Builds nicht unterbrochen werden.
Was du damit machen kannst
- 1Volle Festplatten diagnostizieren und behebenBitte deinen AI-Assistenten zu identifizieren, was den Speicherplatz verbraucht, und diesen zu leeren, wenn du Speicherfehler erhältst.
- 2Spezifische Package Manager bereinigenAnweise die AI, nur alte Cache-Einträge für bestimmte Tools wie npm oder Docker zu entfernen.
- 3Inaktive Projekt-Abhängigkeiten anvisierenLass den Assistenten node_modules oder Build-Ordner aus Projekten finden und entfernen, die du schon lange nicht mehr angefasst hast.
- 4Sichere Dry Runs durchführenFordere eine Vorschau dessen an, was gelöscht würde, um sicherzustellen, dass keine kritischen Dateien verloren gehen, bevor du die Bereinigung ausführst.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du diskdiet MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügendiskdiet MCP in Claude Code installieren
$ claude mcp add diskdiet -- npx -y diskdietdiskdiet MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"diskdiet": {
"command": "npx",
"args": [
"-y",
"diskdiet"
]
}
}
}diskdiet MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"diskdiet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"diskdiet"
]
}
}
}diskdiet MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"diskdiet","type":"stdio","command":"npx","args":["-y","diskdiet"]}'diskdiet MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"diskdiet": {
"command": "npx",
"args": [
"-y",
"diskdiet"
]
}
}
}diskdiet MCP in Codex installieren
$ codex mcp add diskdiet -- npx -y diskdietdiskdiet MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.diskdiet] command = "npx" args = ["-y", "diskdiet"]
diskdiet MCP in Gemini CLI installieren
$ gemini mcp add -s user diskdiet npx -- -y diskdietdiskdiet MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"diskdiet": {
"command": "npx",
"args": [
"-y",
"diskdiet"
]
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarroystondwork-dev/diskdiet is public and reachablegithub.com/roystondwork-dev/diskdiet ↗Bestanden
- Paket nennt dieses Repository als Quellediskdiet names roystondwork-dev/diskdiet as sourcenpmjs.com/package/diskdiet ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for diskdietnpmjs.com/package/diskdiet/v/0.6.3#provenance ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-14github.com/roystondwork-dev/diskdiet ↗Bestanden
- OpenSSF ScorecardOpenSSF Scorecard 7.7 / 10; weakest: Code-Review 0, Maintained 0, CII-Best-Practices 0scorecard.dev/viewer/?uri=github.com/roystondwork-dev/diskdi ↗Bestanden
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from diskdietBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeitenthe package checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehen📖 Documentation: https://roystondwork-dev.github.io/diskdiet/ (install · disk full? · what it cleans)
Why
Package managers never forget. After a year of npm install, the npm cache alone
can pass 40 GB, and Docker images, the pnpm store and old projects' node_modules
add more. Most cleaners either wipe everything, so your next installs crawl, or only
handle one tool.
diskdiet shows the whole picture first, then removes only what you haven't used lately: by default, anything unchanged for 30 days.
Desktop app
Prefer clicking? The diskdiet app shows the same breakdown in a window: how much
can be freed, a bar for every cache, and the node_modules of each project you
haven't touched, which you can untick to keep. Pick an age (7, 30 or 90 days, or
everything), review the list, and free it in one click.
It also stays in your menu bar (or system tray) after you close the window, checks
every few hours, and notifies you when more than 10 GB could be freed. If you want, it
can clean old package-cache entries automatically every day or week, but never
node_modules or Docker (details).
Download it from the latest release:
| OS | File |
|---|---|
| macOS (Apple silicon and Intel) | diskdiet-app_<version>_macos_universal.dmg |
| Windows | diskdiet-app_<version>_windows_amd64_setup.exe (installs for your user, no admin needed) |
| Linux | diskdiet-app_<version>_linux_x86_64.AppImage |
The app isn't signed by Apple or Microsoft yet, so the first launch needs one extra step (details):
- macOS: open the app once, then go to System Settings → Privacy & Security and click Open Anyway.
- Windows: on the SmartScreen warning, click More info → Run anyway.
- Linux:
chmod +x diskdiet-app_*.AppImageand run it.
VS Code
The diskdiet extension adds a Disk space view, a status bar item that appears when
a lot can be freed, and a Free Disk Space… command. When a command in the terminal
fails with "no space left on device", it offers to free space right there
(details). Search diskdiet in the Extensions view, or install the
.vsix from the latest release.
AI assistants (MCP)
Let Claude Code, Cursor, VS Code Copilot and other assistants see what is using disk space and free it when you ask:
claude mcp add diskdiet -- diskdiet mcp
scan_disk_usage changes nothing; free_disk_space removes only what the scan
showed, for the sources you choose, and asks you to confirm
(details).
Claude Code plugin
The plugin adds the MCP tools and a skill that tells Claude when to use them, so "my disk is full" or "no space left on device" gets diagnosed and fixed in the conversation, asking before anything is removed:
/plugin install diskdiet --marketplace roystondwork-dev/diskdiet
Usage
diskdiet # scan: what's using space, what can go (changes nothing)
diskdiet clean # free what's older than 30 days, after showing the list
diskdiet clean --older-than 7d # be more aggressive
diskdiet clean --only npm,docker # just these
diskdiet clean --skip node_modules
diskdiet clean --all --dry-run # what removing everything would free
diskdiet scan --projects ~/code # look for node_modules only under ~/code
diskdiet scan --json # for scripts
| Flag | |
|---|---|
--older-than 30d |
What counts as old: 12h, 7d, 2w… |
--all |
Everything, whatever its age |
--only, --skip |
npm, yarn, pnpm, bun, pip, uv, cargo, go, gradle, maven, playwright, cypress, xcode, docker, node_modules, target |
--projects DIR |
Where to look for node_modules (repeatable; default: your home folder) |
-n, --dry-run |
Show what clean would remove, remove nothing |
-y, --yes |
Don't ask (for scripts and CI) |
--volumes |
Also remove unused Docker volumes |
--force |
Clean even while a package manager is installing |
--keep DIR |
Leave this node_modules or target folder alone (repeatable) |
--json |
Machine-readable output |
What it cleans, and how
| Where | What clean removes |
|
|---|---|---|
| npm | ~/.npm (or npm config get cache) |
Cached packages and metadata older than the cutoff; old npx installs and logs. Content another, newer entry still uses is kept. |
| Yarn | Yarn 1 cache, Yarn 2+ global cache | Package folders and zips older than the cutoff |
| pnpm | pnpm store path |
Packages no project uses, via pnpm store prune; old metadata |
| Bun | ~/.bun/install/cache |
Package folders older than the cutoff |
| pip | pip cache (PIP_CACHE_DIR) |
Cached downloads and built wheels older than the cutoff |
| uv | uv cache dir |
The whole cache via uv cache clean, only with --all (uv's entries depend on each other) |
| Cargo | ~/.cargo (CARGO_HOME) |
Downloaded .crate files, unpacked sources and git checkouts older than the cutoff |
| Go | GOCACHE, GOMODCACHE |
Build cache entries not used for the cutoff (Go records their last use); module versions downloaded before it |
| Gradle | ~/.gradle (GRADLE_USER_HOME) |
Downloaded Gradle distributions and per-version caches and logs older than the cutoff; Gradle manages its shared dependency cache itself |
| Maven | ~/.m2/repository |
Artifact versions downloaded before the cutoff |
| Playwright | ms-playwright cache |
Older browser revisions; the newest of each browser always stays |
| Cypress | Cypress cache | Older Cypress versions; the newest always stays |
| Xcode (macOS) | ~/Library/Developer/Xcode |
DerivedData and iOS/watchOS/tvOS DeviceSupport older than the cutoff; never Archives |
| Docker | your current docker context | Unused images, stopped containers and build cache older than the cutoff; volumes only with --volumes (details) |
| node_modules | projects under your home folder | node_modules of projects where nothing has changed for the cutoff |
| target | Rust (Cargo.toml) and Maven (pom.xml) projects under your home folder |
Their target build folders, for projects where nothing has changed for the cutoff |
Anything removed from a cache is downloaded again the next time a project needs it.
A removed node_modules comes back with npm install (or yarn, pnpm i, bun i).
Safety
- Scan first, always.
cleanshows exactly what it will remove and asks before removing anything. What it removes is what it showed you. - Never outside a cache. Every removal is checked to be inside the cache folder it belongs to; symlinks are never followed.
- The tool's own command where there is one. pnpm and Docker decide what is unused, so nothing a project or a running container needs goes away.
- Not under a running install or build. If
npm install,pnpm add,yarn,cargo build,go test, a Gradle or Maven build or similar is running, diskdiet skips that cache (--forceoverrides). A runningnpm run devor an idle Gradle daemon doesn't count. - Volumes stay unless you add
--volumes.
Install
# npm (any OS): run it without installing
npx diskdiet
# PyPI (any OS)
pipx install diskdiet # or: uv tool install diskdiet
# Go 1.26+
go install github.com/roystondwork-dev/diskdiet/cmd/diskdiet@latest
# Homebrew (macOS, Linux)
brew install roystondwork-dev/tap/diskdiet
# Scoop (Windows)
scoop bucket add roystondwork-dev https://github.com/roystondwork-dev/scoop-bucket
scoop install diskdiet
# winget (Windows)
winget install roystondwork-dev.diskdiet
Archives, .deb, .rpm and .apk packages for amd64 and arm64 are on the
releases page. The checksum file
is signed with cosign (keyless) and releases include SBOMs and build provenance
(how to verify).
Demo mode
DISKDIET_DEMO=1 diskdiet (or the app started with DISKDIET_DEMO=1) shows made-up
caches and removes nothing: for trying diskdiet, screenshots and recordings.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success (including "nothing to free" and answering no) |
| 1 | Error |
| 2 | Wrong usage, such as an unknown flag or source |
| 3 | clean finished, but some items could not be removed |
Roadmap
v0.2: a desktop app for macOS, Windows and Linuxv0.3: a menu bar / tray icon that warns when caches grow, with optional scheduled pruningv0.4: pip, uv, Cargo, Go, Gradle, Maven, Playwright, Cypress, Xcode, target foldersv0.5: an MCP server for AI assistantsv0.6: a VS Code extension, npm and PyPI packages, the MCP Registry, a Claude Code plugin, winget, demo mode
Ideas and bug reports are welcome in issues.
Contributing
See CONTRIBUTING.md, GOVERNANCE.md and SUPPORT.md. Please follow the Code of Conduct and report vulnerabilities privately as described in SECURITY.md. diskdiet collects no data (privacy).
License
MIT © 2026 Royston D and diskdiet contributors
diskdiet MCP Fragen
Wie füge ich diskdiet MCP zu Claude Code hinzu?
Führe claude mcp add diskdiet -- npx -y diskdiet in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich diskdiet MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie arbeitet der MCP server mit AI-Assistenten zusammen?
Der Server stellt Tools bereit, mit denen Assistenten wie Claude Code oder Cursor sehen können, was Speicherplatz verbraucht, und diesen auf Anfrage freigeben können.
Ist es sicher, diskdiet zur Speicherbereinigung zu nutzen?
Ja, er scannt zuerst und fragt vor dem Löschen nach einer Bestätigung. Zudem wird sichergestellt, dass Löschvorgänge auf die festgelegten Cache-Ordner beschränkt bleiben.
Was passiert mit meinen Projekten nach der Bereinigung?
Alles, was aus einem Cache entfernt wurde, wird bei Bedarf einfach neu heruntergeladen. Entfernte node_modules können mit einem Standard-Install-Befehl wiederhergestellt werden.