Provides end-to-end encrypted cloud storage on the Walrus network via a command-line interface and MCP access.
Also known as needmoretruth/nmts-cli, @needmoretruth/nmts-cli
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
What is nmts-cli MCP?
nmts-cli provides end-to-end encrypted cloud storage on the Walrus network via a command-line interface and MCP access.
Summary generated from the project's README
About nmts-cli MCP server
Storing end-to-end encrypted files on the Walrus network is what nmts-cli enables for developers and AI agents. This tool provides a command-line interface and MCP access to a storage system where encryption occurs locally on your machine, ensuring that file contents, names, and folders remain sealed from the server. The underlying data resides on the Walrus public storage network and is managed via the Sui chain.
Users interact with the system using an NMTS key for decryption and an API key for server communication. The tool supports various operations through commands like nmts put for uploading files, nmts get for downloading, and nmts ls for listing contents. Because storage is leased for specific periods rather than owned forever, users can manage file lifespans using nmts extend to pay for more time from a Sui wallet. It is designed to run on Linux, macOS, and Windows using Node.js, making it suitable for local development or automated environments like CI runners.
Written from the project's README. Every use case is checked against a quote from it.
How to install nmts-cli MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall nmts-cli MCP in Claude Code
$ claude mcp add nmts-cli -- npx -y @needmoretruth/nmts-cliInstall nmts-cli MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"nmts-cli": {
"command": "npx",
"args": [
"-y",
"@needmoretruth/nmts-cli"
]
}
}
}Install nmts-cli MCP in VS Code
.vscode/mcp.json
{
"servers": {
"nmts-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@needmoretruth/nmts-cli"
]
}
}
}Install nmts-cli MCP in VS Code CLI
$ code --add-mcp '{"name":"nmts-cli","type":"stdio","command":"npx","args":["-y","@needmoretruth/nmts-cli"]}'Install nmts-cli MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"nmts-cli": {
"command": "npx",
"args": [
"-y",
"@needmoretruth/nmts-cli"
]
}
}
}Install nmts-cli MCP in Codex
$ codex mcp add nmts-cli -- npx -y @needmoretruth/nmts-cliInstall nmts-cli MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.nmts-cli] command = "npx" args = ["-y", "@needmoretruth/nmts-cli"]
Install nmts-cli MCP in Gemini CLI
$ gemini mcp add -s user nmts-cli npx -- -y @needmoretruth/nmts-cliInstall nmts-cli MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"nmts-cli": {
"command": "npx",
"args": [
"-y",
"@needmoretruth/nmts-cli"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableneedmoretruth/nmts-cli is public and reachablegithub.com/needmoretruth/nmts-cli ↗Pass
- Package names this repository as its source@needmoretruth/nmts-cli names needmoretruth/nmts-cli as sourcenpmjs.com/package/@needmoretruth/nmts-cli ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @needmoretruth/nmts-clinpmjs.com/package/@needmoretruth/nmts-cli/v/0.59.1#provenanc ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/needmoretruth/nmts-cli ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @needmoretruth/nmts-cliPass
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubnmts
Command-line access to NMTS: NeedMoreTruthStorage, end-to-end encrypted cloud storage on the Walrus network, built by one developer (needmoretruth). For people at a terminal, and for the AI agents they run.
한국어 문서, Talk about NMTS on Discord, in English or Korean.
If you are an AI agent, read AGENTS.md instead. It has the tier table, the exit codes and the rules for a run nobody is watching.
Status: early. The interface may still change before 1.0. A command added after this file was written is in
nmts --help.
🧭 What NMTS is
Storage where the encryption happens on your machine and the keys never leave it. The server receives sealed bytes it cannot open. File contents, names and folders all live inside a sealed list that only your NMTS key opens.
The bytes live on Walrus, a public storage network, paid for on the Sui chain.
- Storage is bought for a period, not forever. A file has a lease. It can be extended, and NMTS warns before one runs out.
- There is no password reset. Your NMTS key is the account. It cannot be recovered or changed while keeping the files, because nobody, NMTS included, holds a key to them.
- NMTS charges nothing. Storage is bought from the Walrus network, for a period, from your own
wallet. Nothing is paid to NMTS. Uploads here spend credits, which are storage a donation pool
has already paid the network for (the weekly free trial). They are not sold. One command,
nmts extend, pays from your own Sui wallet instead, and asks for a separate agreement first, because a signed purchase on a public chain cannot be reversed by anyone.
This tool, the encryption engine and the recovery program are open source under Apache-2.0. The server and the web app are not published.
📦 Install
Node 22.15.0 or newer. Nothing is compiled at install time and there is no native build step: the encryption engine is a WebAssembly module carried in the repository. It runs wherever Node runs: Linux, macOS, Windows, and inside a rootless container.
npm install -g @needmoretruth/nmts-cli
nmts --help
The same package can be installed straight from this repository, without the registry: from the default branch, from a pinned version, or from the tarball attached to the latest release:
npm install -g github:needmoretruth/nmts-cli # the default branch
npm install -g github:needmoretruth/nmts-cli#v0.60.1 # a pinned version
npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz
The registry name carries the scope: npm install -g nmts finds nothing, because the registry refuses
that short name as too close to names already published.
To work on the source instead, see CONTRIBUTING.md.
🔄 Staying up to date
nmts update # installs the newest release over this one
nmts update --dry-run # prints the versions and the command, changes nothing
Separately, once a day after a command finishes, the tool asks the releases page which version is
newest and remembers the answer. When a newer one exists, the next run prints one line on stderr.
That request carries no NMTS key, no API key and no command name, and it is the only request
the tool makes that no command asked for. Setting NMTS_NO_UPDATE_CHECK to anything stops both
halves, and nmts env shows what the check last found.
🚀 First run
nmts env # what this machine is, and whether credentials are in reach. Contacts nothing.
nmts login # keep the NMTS key here, sealed, and take an API key
nmts ls # list the files
nmts put x # upload one file; spends credits
nmts get x # download one file
Run nmts env first on any machine you do not know: a container, a CI runner, someone else's
laptop. It needs no credential and reports what a credential here would be exposed to.
🔑 The two credentials
| What it does | How to give it | |
|---|---|---|
| NMTS key | Opens your files. Every key in the account derives from it. Never goes to the server. | NMTS_ACCOUNT_CODE_FILE=/path (recommended), nmts login, NMTS_ACCOUNT_CODE |
| API key | Makes the server answer. Made on the account screen at nmts.me. Opens no file. | NMTS_API_KEY_FILE=/path (recommended), NMTS_API_KEY, nmts login |
nmts ls needs both: the API key so the server answers, your NMTS key so the answer can be opened.
The NMTS key used to be called the account code. Only the name changed. The flags, the
environment variables (NMTS_ACCOUNT_CODE, NMTS_ACCOUNT_CODE_FILE), the config keys, the MCP
tool and argument names, the error codes and every file format keep the names they already had, so
nothing you have scripted breaks.
nmts login checks the API key with the server before writing it down, prints that key's public
handle and never the key itself, and does not replace a stored API key unless the run says so.
nmts logout clears what is stored.
nmts whoami --reveal prints your NMTS key itself. It is locked until you run nmts unlock reveal once, and asked about on every run. Anything that logs your terminal has your NMTS key from
then on. Add --phrase for the same key as its 15-word recovery phrase (--lang ko for Korean
words). nmts login accepts either form.
Neither credential is ever accepted as a command-line argument. Any process can read another process's command line, and shells record it in history. There is no flag for either.
Where the NMTS key can live
| What it does | Asks | |
|---|---|---|
NMTS_ACCOUNT_CODE_FILE=/path |
Reads your NMTS key from a file it never copies | nothing |
nmts login |
Seals it under a passphrase at ~/.nmts/credentials.json |
nothing |
nmts login --plain |
Writes it in the clear, mode 600 | once, unsafe-code-storage |
NMTS_ACCOUNT_CODE, holding your NMTS key |
Uses it straight from the environment | once, plain-env |
A sealed NMTS key needs its passphrase for every command, from a terminal or from
NMTS_PASSPHRASE. Opening it costs a fraction of a second and 64 MiB of memory, which is what
makes guessing the passphrase expensive. A passphrase does not protect your NMTS key from anything
running as you: on a machine where an agent runs unattended, the passphrase has to be reachable
too. That is why the file form is the recommendation for agents: your NMTS key is never copied,
and the permissions are the host's to set.
An environment variable is not private: docker inspect prints it, anything running as you can
read /proc/<pid>/environ, every child process inherits it, and CI systems write it into logs.
That is why using one asks once. nmts login --env prints the line to set and writes nothing. It is
behind the same agreement.
Under Codex, Hermes and OpenClaw an environment variable does not reach an MCP server. All
three clear the environment before starting one. Sign in with nmts login instead, or put the
variables in the server's own env block. nmts env names the agent it can see.
🤖 Before you hand this to an agent
Your NMTS key is everything at once. A program that has it can read every file, upload,
delete and sign with the wallet, and its requests cannot be told apart from yours. It cannot be
rotated while keeping the account. Give an agent its own account, made with nmts create, not
your main one.
🧰 Commands
| Command | What it does |
|---|---|
nmts env |
Where this is running, and what that means. Needs nothing. |
nmts login / logout |
Keep or remove an NMTS key and an API key on this machine |
nmts whoami |
Which account the stored NMTS key belongs to, offline. --reveal prints your NMTS key |
nmts ls |
List the files |
nmts usage |
What the account holds: counts, bytes, the largest files, the trash |
nmts balance |
Credits left, what they buy, and the ceilings on spending |
nmts get <path> |
Download one file, decrypt it, check it |
nmts pull [folder] |
Download a whole folder, or the whole account, keeping its shape |
nmts put <file> |
Encrypt one file and upload it. Spends credits. --deposit <n> sets the deposit for this upload |
nmts push <directory> |
Upload a whole directory, keeping its shape. Spends credits. --deposit <n> applies to every file in it |
nmts rm <paths> |
Move things to the trash, restorable for 30 days |
nmts restore <paths> |
Bring things back out of the trash |
nmts sweep |
Drop trash entries past their 30 days. Cannot be undone. Asks every run |
nmts erase <paths> |
Erase files for good: the server's record and this account's key, trash or not. A typed sentence, your NMTS key beside the API key. --release-storage also destroys credit-paid storage (locked until nmts unlock release-storage) |
nmts mkdir <path> |
Make a folder, and any folder above it that is missing |
nmts mv <paths> <folder> |
Move things into a folder. / is the top of the drive |
nmts rename <path> <name> |
Give one thing a new name |
nmts star / unstar |
Star files, or take the star off |
nmts pin / unpin |
Hold files at the top of their folder, or let them fall back |
nmts label <name> <files> |
Put one label on files. unlabel takes it off. --rename and --all sweep the whole list |
nmts on-collision |
What an upload does when its name is already taken |
nmts padding [mode] |
How file sizes are hidden on the storage network, and change it for the next uploads |
nmts deposit [credits] |
How many credits each credit-paid upload sets aside as a deposit (0 to 64, default 64), and change it |
nmts tip [percent|off] |
A standing share of every WAL payment sent to the developer as a gift (default 0). Setting it needs nmts unlock donate. The agreement is asked once |
nmts expiring |
Which files run out of bought storage soon, and when |
nmts losses |
Storage NMTS bought for you that the daily check could not find on the chain. --recheck <id> asks again. --dismiss <id> takes a line off |
nmts extend <path> |
Buy more storage time for one file. Signs and spends from the wallet |
nmts wallet |
The account's wallet address, and its SUI and WAL balances. Never signs |
nmts wallet activity |
The wallet's recent transactions, named only where the chain proves it. Never signs |
nmts wallet storage |
The storage resources (size × time) the wallet holds outside any file. Never signs |
nmts wallet storage split <id> --size <n>|--epochs <n>, merge <id> <id>, transfer <id> <address> |
Cut, join or hand over a storage resource. Signs, under the wallet unlock (transfer needs scope all). No file goes with a transfer: size and remaining time only |
nmts wallet send <SUI|WAL> <amount|max> <address> |
Send coins to an address. Signs and spends from the wallet. Prints the review. Sends only with --yes |
nmts wallet swap <SUI|WAL> <amount|max> |
Swap one coin for the other on DeepBook or Bluefin. Signs and spends from the wallet. Without --venue prints both quotes and stops. Swaps only with --yes |
nmts wallet donate <SUI|WAL> <amount> |
A voluntary gift to the developer, in either coin. Signs and spends. Locked until nmts unlock donate, and --yes every run |
nmts wallet hall [--name <name>|--remove] |
The gift hall of fame. --name lists you by a name you choose, signed by your wallet |
nmts trial |
What is left of this week's free credits. trial apply asks for some |
nmts create |
Make a NEW account and print its NMTS key once. Nothing can print it again. With no verified API key on this machine it makes the NMTS key here, prints an address, and waits while a person opens it, types that NMTS key and passes the human check. The account exists the moment they finish. --no-wait prints the address and stops |
nmts verify |
Ask a person to pass the check that opens this account's limits. Only the account holder can: signed in to this account in that browser, or typing its NMTS key there |
nmts public-code |
The code other accounts send files to. --publish makes it reachable. --save [file] writes your public code file |
nmts public-code list · new · revoke <n> |
Every code your NMTS key has published. Publish the next one (--replace <n> revokes one in the same step). Revoke one: nobody can send to it again. Revoking asks every time |
nmts share <path> <address> |
Give one file to another account. Withdrawing does not recall it. Locked until nmts unlock share. Every share stops and --yes answers for that one file |
nmts shares |
What was shared with this account. --sent <path> shows who one file went to |
nmts receive <id> |
Download one file somebody shared with this account |
nmts unshare <id> |
Withdraw a share you sent, or remove one you were sent |
nmts handover make <path> --to <public code | public code file> |
Write a handover file for one account and pass it on yourself. It cannot be taken back, and NMTS keeps no record of it. Locked like share |
nmts handover open <file> |
Download the file a handover file carries. Needs the NMTS key and no API key. Tells the NMTS server nothing about the file |
nmts link make <path> [--hide-name] [--expires <n>d] |
Make a public link to a file |
nmts link list <path> |
List a file's public links |
nmts link revoke <id> |
Cut a public link |
nmts link open <link> [--out <path>] |
Download and decrypt a file from a public link, without logging in |
nmts rebuild |
Build a file list from the server's rows, for an account with none |
nmts rollback |
Put the previous version of the file list back. Locked until nmts unlock rollback, --yes every run |
nmts listfile |
Write this machine's copy of the sealed file list out as a file |
nmts recovery-list |
Write the file that finds this account's bytes without NMTS |
nmts kit |
Recovery kit: that list and your NMTS key, together in one file |
nmts recovery |
Download the standalone program that reads files back without NMTS |
nmts unlock / nmts lock |
What this machine has unlocked. unlock <key> opens one (a person, at a terminal), lock <key> closes it. consent is the older name |
nmts mode |
How much an agent driving this tool may decide without asking |
nmts support send |
Send a report to the developer: a bug, an error, an idea, a question. --attach-log adds the last runs, redacted |
nmts support list / show <code> / reply <code> |
Read the answers, and write back in the same thread |
nmts update |
Install the newest published release of this tool |
nmts notices |
What NMTS has posted: interruptions, incidents, and the warning before new Terms take effect. notices <id> prints one. --save <id> keeps it as a dated file |
nmts terms |
The Terms of Service in force. --lang ko for Korean, --board for the message board's terms, --save to keep a copy |
nmts privacy |
The Privacy Policy in force. --lang ko, --save to keep a copy |
nmts delete-account |
A person erases this account's server record. Irreversible. Needs your NMTS key and a typed sentence. Refused in the auto modes, and under skip-permissions only with --reason |
nmts accept-terms |
Accept a new version of the Terms after reading it: a person types the versions, or an agent relays them with --accept-terms <v> --accept-privacy <v> --yes after asking |
nmts key new |
Make an API key for this account with your NMTS key alone, no browser. --scopes read,write,spend, --days <n>. The new API key is stored as this machine's credential. --print also prints it once |
nmts devices |
The devices signed in to this account. --sign-out <id> or --sign-out all ends one or all of them. Needs your NMTS key, locked until nmts unlock sign-out, asked every run |
nmts mcp |
Serve a subset of the above as tools over the Model Context Protocol |
nmts s3 |
Serve the drive to any S3 program, on this machine only |
nmts platform keygen |
Make the Ed25519 key pair a business signs its NMTS Platform requests with: both halves go to a file only you can read (mode 0600), and only the public half is printed. The public half is registered at nmts.me under Settings › Developer › Platform |
Listing and fetching
ls takes --json, --all (include the trash. The count always says how many were hidden),
--find <text> (files whose name contains the text, with the folders that hold them), --sort name|size|date and --desc.
get takes --out and --force. It never leaves a half-right file: the bytes are written under a
temporary name in the same directory and renamed into place only once the whole-file hash
matches. One part is held in memory at a time, not the file. --out - sends the file to stdout
instead of writing it, with everything a person reads on stderr. A pipe cannot be taken back, so
that mode proves the whole file first and refuses above 64 MiB.
pull fetches each file on its own. One that will not come back is named at the end and the rest
stay on disk. Files already in the destination are skipped and counted. --force replaces them.
Uploading
nmts put report.pdf --dry-run # what it would cost. Sends nothing, charges nothing.
nmts put report.pdf --to notes # into an existing folder
nmts put film.mov --part-size 256MiB # bigger parts: fewer purchases, more memory
One credit per started mebibyte, printed before anything is spent. A name already taken in that
folder gets a numbered copy (report (2).pdf) unless nmts on-collision says otherwise. NMTS keeps
no previous versions, so replacing is permanent. A file larger than one part (64 MiB by default) is
split and each part bought separately. A run that stops partway is finished by running the same
command again, which buys only the parts that were never bought. The same is true after any
interrupted upload: the retry costs nothing more.
--pay wallet buys the storage from the wallet your NMTS key derives instead of from credits:
nmts put film.mov --pay wallet --dry-run # the review: WAL price, tip, fee, balances, days. Signs nothing
nmts put film.mov --pay wallet --epochs 6 # six of the storage network's epochs (default 2)
nmts put film.mov --pay wallet --storage fit # use a storage resource the wallet already holds, cut to size
nmts put film.mov --pay wallet --sui-key-file ~/.sui/agent.key # another Sui wallet you hold pays instead
The file is planned into the same parts, the chain quotes each part in WAL
and the relay's tip in SUI, the register transaction is dry-run for its fee, both balances are read,
and the review is printed (the term as epochs and as days) before the wallet agreement (scope
storage) is held against the total and anything is signed. A wallet known to be short is refused
with the two numbers. A balance that could not be read is said as unread, not as zero. Each part
takes two signatures, register and certify. A run that stops partway is finished by running the same
command again, which signs nothing twice. --storage fit|whole|<object id> uses a free storage
resource the wallet holds (nmts wallet storage lists them) for a one-part file: fit cuts it to the
part's encoded size and leaves the rest free, whole binds all of it with the file, and the review
says in bytes which. Without --storage new storage is bought. The review only mentions what the
wallet holds. The server records the file as stored on the wallet's own storage, and nmts extend
can extend it. A wallet-paid upload does not carry the recovery list's storage-network copy,
whichever way the account's switch is set. Today only the browser's small-file uploads do. push --pay wallet does the same one file at a time.
With --sui-key-file <file>, put pays from another Sui wallet you hold instead of your NMTS key's
wallet, and the review names that wallet. The file holds the wallet's suiprivkey1… line. A file other
users can read is refused, and the key is never printed. It cannot be combined with --wallet or used
with push.
push uploads a directory and stops at the first failure, saying what is already uploaded.
Files whose name is already in the destination are skipped, so running it again is safe. Names
beginning with a dot are left alone unless --hidden is given, and symbolic links are not followed.
nmts deposit shows how many credits each credit-paid upload sets aside as a deposit, and nmts deposit <n> changes it for every device's next uploads (0 to 64, default 64). The deposit pays the
chain fee of a later operation on that file (releasing its storage early, for instance), measured
rather than spent whole, and what is left comes back when the storage period ends. put --deposit <n> and push --deposit <n> set it for one run. --deposit 0 sets nothing aside: that file still
releases, but pays twice the same fee out of the balance at that moment, and is refused with both
numbers named when the balance cannot cover it.
nmts padding shows how file sizes are hidden, and nmts padding standard, nmts padding pow2 or
nmts padding off changes it for every device's next uploads (off stores the exact size: the
file's length is visible to the network and to anyone who reads the blob, for about 1 % less storage). Anyone can read the size of a piece on the storage
network. Blank bytes make that size one of a set of fixed values. Powers of two hide more and cost
more storage on average.
Names, folders and the trash
nmts mkdir photos/2026/august # makes all three if they are missing
nmts mv report.pdf photos # `/` moves it back to the top of the drive
nmts rename report.pdf "q3 report.pdf"
nmts rm photos/2026 # to the trash, with every file under it
nmts restore photos/2026
None of these costs anything or asks anything: a name, a folder and a parent live only in your
sealed file list, and the server holds no place to put a name. rm never destroys. Each trashed
file keeps its own thirty-day clock. The command that erases for good is deliberately not in this
tool. A path is matched whole (photos/a.jpg is not a.jpg), and a path that matches two entries
is refused rather than resolved. rm, restore and mv take several paths in one write. A path
that names nothing stops the whole run before anything is touched.
nmts label --rename <old> <new> renames a label on every file that carries it, and
nmts unlabel <name> --all takes it off all of them. Both change only the file list.
nmts-cli MCP questions
How do I add nmts-cli MCP to Claude Code?
Run claude mcp add nmts-cli -- npx -y @needmoretruth/nmts-cli in your terminal. Add --scope user to make it available in every project.
How do I add nmts-cli MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How is my data secured?
Encryption happens on your local machine and the keys never leave it; the server only receives sealed bytes it cannot open.
Can I recover my account if I lose my key?
No, there is no password reset because your NMTS key is your account and nobody else holds a copy of it.
Does NMTS charge fees for storage?
NMTS itself charges nothing; you pay the Walrus network directly from your own wallet for storage leases.
Is the tool compatible with Windows and macOS?
Yes, the encryption engine is a WebAssembly module that runs wherever Node runs, including Linux, macOS, and Windows.