NullDisk for AI Agents: JSON Reports, Schemas and MCP Scope

Create a structured report

The standalone CLI provides JSON/NDJSON reports, capability discovery, schemas, and explicit work budgets. The commands below inspect data and write local reports.

nulldisk capabilities
nulldisk schema scan > disk-schema.json
nulldisk scan ~/Downloads --json --timeout 30 > disk-report.json
nulldisk dev ~/src --json > development-report.json

Check exit status: 0 means complete within the selected scope; 3 means partial data or a reached budget; 130 means interrupted. Preserve the incomplete indicators so an assistant cannot mistake a partial scan for a complete inventory.

Review paths, folder names, and Git metadata before sending a report to an external service. Share only the information needed to explain a storage problem. Local scan processing does not make a report private once you upload it.

Ask for a reviewable plan

Ask the assistant to identify large locations and explain what further evidence is needed. A folder’s name, age, or size does not establish that it is safe to delete. Development reports distinguish rebuildable output, worktrees to review, and items to keep.

Where MCP fits

MCP is a protocol for exposing tools to assistants. JSON output alone is not an MCP integration. The workflow on this page uses CLI reports rather than an MCP server. Check installed capabilities and integration documentation before adding an agent configuration.

Review cleanup separately

Use the Mac collector, Development Cleanup, or CLI review to inspect the current source and selected action. The CLI clean command defaults to a dry run; explicit cleanup rechecks file identity and Git evidence. Trash, permanent removal, and Git worktree removal have different recovery implications.

Privacy

The Mac app sends anonymous usage telemetry without file names, paths, or contents. See the privacy policy. Remote storage and any assistant you choose introduce their own connections and data handling.

Common questions

Does this page provide a NullDisk MCP server?

No. The available workflow described here uses the standalone CLI’s JSON/NDJSON reports and schemas. Check your installed CLI’s capabilities before configuring an integration; a JSON report is not an MCP server.

Can an assistant read my private paths?

A shared report can reveal paths and folder names. Inspect and redact it first. Sending it to an assistant makes that service’s data-handling rules relevant even though the scan ran locally.

Will reporting commands delete files?

The scan and dev commands inspect metadata and Git evidence. Cleanup is a separate operation through clean or the interactive review; clean is a dry run unless explicitly enabled.

Give your assistant measurements you can review.