The command-line tool — nmts-cli
A command called nmts, run from a terminal on Node 22 or newer. It does from a terminal what the browser does — uploads and downloads, folders and listings, sharing, credits and the wallet, and the recovery files.
npm install -g github:needmoretruth/nmts-cliAdding it to an AI agent is one line. Claude Code and Codex take the same syntax, and opencode takes the same command in its configuration file. Once it is added, the agent uses the account through this tool. The account code is kept on that machine, so the tool says what that means before it does it. Three things ask once per machine: spending money, anything that cannot be undone, and the account code going anywhere outside the tool's own locked file.
claude mcp add nmts -- nmts mcp --out ~/nmts
codex mcp add nmts -- nmts mcp --out ~/nmtsThe repository contains AGENTS.md, which is the instructions written to be read by an agent rather than by a person: what to call in what order, and where a person has to decide.
API
The server speaks HTTP at nmts.me/v1, and an agent key made on the account screen is what opens it. A key can do what was ticked when it was made and nothing else: read what is stored, upload and delete files, buy storage with credits. It does not reach the account screen, the signed-in devices, or anything that cannot be undone.
A key is not the account code. The key opens the server; the key that opens the files is derived from the account code. There is no separate list of endpoints. That list is the command-line tool's source, which is a program making those same requests.
The recovery program — nmts-recovery
One executable, for Linux, macOS and Windows. Give it a recovery list file and your account code and it fetches the pieces from the storage network and puts your files back together. It does not connect to an NMTS server.
It runs from a terminal; --gui opens a screen you click instead. The recovery list file is downloaded from the account screen beforehand. The built executables and the source are in the same place.
The encryption engine — nmts-crypto
The Rust library the browser and the recovery program both use. It derives the keys from an account code, encrypts files, and opens them again.
Because both programs use the same code, a file encrypted in the browser opens in the recovery program with no NMTS involved. The format documents are in the same place.
Licence
All three published repositories are Apache-2.0. Run them, change them, build on them — including in a commercial product — keeping the licence and copyright notices, and saying in changed files that you changed them. They were AGPL-3.0 until 30 August 2026; copies already held under that licence stay under it.
What is not published
The server and the web app are not open source. What is published is the three repositories above.
There is no way for you to check that the code your browser was handed is the code in that repository. The command-line tool and the recovery program do not have that problem: the file you downloaded is the file that runs.