
Armadoc
link.armadocv0.1.0Updated Oct 6, 2026
Send and read end-to-end encrypted documents. Your private key never leaves your machine.
Overview
Lets an assistant list, decrypt to disk, and send end-to-end encrypted Armadoc documents from your own machine.
- What it does
- Armadoc is a local stdio MCP server plus CLI for end-to-end encrypted document sharing. Its tools list documents sent to and by you, decrypt a document's files to disk (by default under a Downloads folder keyed by link ID), and encrypt local files to send or invite a recipient who has no key yet. Reading returns file paths rather than contents, so text enters the assistant's context only if it opens the file.
- When to use it
- Use it when you want an assistant to handle encrypted document exchange on your behalf while the private key and plaintext stay on your computer. It suits desktop setups where you read or send documents interactively; it is not meant for cloud-hosted agents.
- Requirements
- Node 24 or later, installed globally via npm and run as the local command armadoc mcp over stdio. Pairing requires running armadoc login in a browser on the same machine, which enrolls a key for that machine. The server must run on your own computer next to the MCP host; no environment variables or headers are declared.
Installation
In SourceWeft
- Open Armadoc in the dashboard and add it to a workspace.
- 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
armadoc
The armadoc CLI and a local stdio MCP server for Armadoc end-to-end
encrypted document sharing. Your agent sends and reads documents as you; the private key and the
plaintext never leave your machine.
Install
Node 24 or later.
Pair
This pairs this machine with your Armadoc account in a browser and enrolls a key for it. The key opens only what is sent to you after pairing; anything sent earlier still opens wherever you read it before.
armadoc status shows the pairing.
Add to an MCP host
The server is armadoc mcp, over stdio. Hosts with a JSON config take:
Requests from the server include the name and version your MCP host reports for itself, so Armadoc can see which hosts are in use.
The server has to run on your own computer, next to your MCP host. It won't work in cloud-hosted
agents, because armadoc login needs a browser on the same machine. Even if it could pair there,
your private key and the documents you read would sit on the provider's machines, possibly after
the session ends.
Tools
read_document returns file paths, not contents: what a document says enters the agent's context
only if the agent opens the file.
Uninstall
armadoc logout deletes the private key and credentials in ~/.config/armadoc. The agent stays on
your account until you remove it in settings, and documents it read stay in ~/Downloads/armadoc.
Source: packages/cli/README.md at commit 6ea183c
Tools
0Version history
1- v0.1.0LatestOct 6, 2026


