Filewash

io.github.cassilupPublished by GitHub account cassilupv0.1.0Updated Oct 24, 2026

Privacy-first file tools for AI agents — PDF & image ops, metadata scrubbing, background removal.

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

Lets an assistant process PDFs and images locally — merge, split, rotate, compress, convert, resize, strip metadata, and remove backgrounds.

What you can do
Filewash exposes eleven file-processing tools to an agent: PDF merge, split, rotate and metadata stripping, plus image compression, format conversion, resizing, EXIF/GPS/ICC/XMP metadata stripping, background removal, watermarking, and QR code generation. It runs as a local stdio MCP server started with node, and the same logic is also offered as a metered REST API and an npm SDK. Processing is described as in-memory with no file contents logged.
When to use it
Useful when an assistant needs to prepare documents or images before they are shared or fed to a model, especially in workflows where files should not be uploaded to a third-party service. Metadata scrubbing and background removal are the less common capabilities it highlights.
Requirements
A local Node.js runtime; the manifest declares no authentication, environment variables, or headers. The README's REST API examples use a bearer key named FILEWASH_KEY, but that applies to the hosted API, not the local stdio server. Desktop-only; no web executable.
Before you install
The MCP server writes output files to paths you pass, so it can create or overwrite files on disk. The hosted REST API is metered and priced by plan, and its examples send files to a remote endpoint with a bearer key; the local server avoids that upload. Treat the privacy and zero-retention claims as vendor statements.

Installation

In SourceWeft

  1. Open Filewash 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

filewash — privacy-first file tools for AI agents

The file-processing layer for agents and apps that can't send files to a third party. Compress, convert, resize, merge/split PDFs, strip metadata, and remove backgrounds — exposed as an MCP server, a metered REST API, and an npm SDK. Zero-retention by default: files are processed in memory and never stored or logged.

Built from filewash.app's client-side WASM tools. Same logic, now callable by your agents.

Why this exists

Every other file-tools API and MCP server is a wrapper around an upload-to-server service. That's a non-starter for legal, healthcare, finance, and any GDPR-bound workflow — and it's a liability when you're piping documents into an LLM. filewash is the one built around not keeping your files, with two tools nobody else ships as an MCP: background removal and metadata scrubbing.

MCP server (Claude Desktop, Cursor, Claude Code)

jsonc
// claude_desktop_config.json  →  mcpServers{  "filewash": { "command": "node", "args": ["/path/to/filewash-api/src/mcp/server.js"] }}

Your agent now has 11 tools. Ask it: "strip the location metadata from these photos before I upload them" or "merge these contracts and rotate the scanned pages."

REST API

bash
# discovercurl https://api.filewash.app/v1/tools
# strip EXIF/GPS from a photo (returns the cleaned image)curl -X POST https://api.filewash.app/v1/tools/image_strip_metadata \  -H "Authorization: Bearer $FILEWASH_KEY" \  -F '[email protected]' -o clean.jpg
# merge PDFscurl -X POST https://api.filewash.app/v1/tools/pdf_merge \  -H "Authorization: Bearer $FILEWASH_KEY" \  -F '[email protected]' -F '[email protected]' -o merged.pdf

Every response carries X-Filewash-Meta (operation result) and X-Filewash-Quota-Remaining.

Tools

ToolCategoryWhat it does
pdf_mergepdfMerge PDFs into one
pdf_splitpdfExtract specific pages
pdf_rotatepdfRotate pages by 90°
pdf_strip_metadataprivacyRemove author/title/producer/dates
image_compressimageLossy re-encode at a target quality
image_convertimagejpeg ↔ png ↔ webp ↔ avif
image_resizeimageResize (never upscales)
image_strip_metadataprivacyStrip EXIF/GPS/ICC/XMP
image_remove_backgroundimageRemove background → transparent PNG (local AI model, no upload)
image_watermarkimageTile a text watermark
qr_generategenerateQR code PNG from text/URL

Pricing (planned)

PlanPriceQuotaRetention
Free$0100 ops/moin-memory
Pro~$19/mo10,000 ops/moin-memory
Business~$99/mounlimitedzero-retention guarantee + audit log + BAA

Run locally

bash
npm installnpm run test:engine   # 10 tools, end-to-end, no browsernpm run mcp           # stdio MCP servernpm run rest          # REST API on :8787  (try key "demo")

Privacy

No file is written to disk by the REST API; the MCP server writes output only to the path you pass. No file contents are logged. The Business tier adds a contractual zero-retention guarantee and audit logging.

Source: README.md at commit 72a9aef

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% 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