for AI agents
Send files from your AI agent.
Your agent sends an .env file, a key or a finished report to a person. The file is encrypted on your computer, the
recipient downloads it once, and then it no longer exists. The model never sees the download link or its key and sees the password only if you let it send it.
Install
You need a VitalSend account. A free account sends a few files a month. Pick your app:
Add the marketplace and install the plugin:
/plugin marketplace add vitalsend/mcp /plugin install vitalsend@vitalsend Or as a plain MCP server, from a terminal:
claude mcp add vitalsend -- npx -y @vitalsend/mcp - Download vitalsend.mcpb.
- Open the file. Claude Desktop shows the extension; click Install.
- Choose the folder the tool may send files from, for example a project folder. Not your whole home folder.
Claude Desktop runs the extension with its own Node.js, so there is nothing else to install.
Add the marketplace in a terminal and install the plugin:
codex plugin marketplace add vitalsend/mcp codex plugin add vitalsend@vitalsend Or as a plain MCP server:
codex mcp add vitalsend -- npx -y @vitalsend/mcp Or by hand, in ~/.cursor/mcp.json, or .cursor/mcp.json in a project:
{
"mcpServers": {
"vitalsend": { "command": "npx", "args": ["-y", "@vitalsend/mcp"] }
}
} Cursor for teams: an admin imports the marketplace vitalsend/mcp from GitHub under Dashboard → Plugins & MCPs.
From a terminal:
code --add-mcp '{"name":"vitalsend","command":"npx","args":["-y","@vitalsend/mcp"]}' Then use it from Copilot Chat in agent mode.
Create an API key under Connected apps on your account page, optionally limited to a list of recipients, and add it to the tool's settings. With an API key every send names a recipient, the link is emailed, and there is no password.
"env": { "VITALSEND_API_KEY": "vsk_…" } claude.ai, ChatGPT and other apps in the browser cannot run a local tool, and the file has to be encrypted on your computer. Point them at https://vitalsend.eu/mcp and they will explain how to install it in an app that can.
Use
Ask your agent: “Send .env to [email protected] with VitalSend.” The first time, your browser opens on vitalsend.eu to sign in and allow the connection. Then, for every send:
- Your app asks you to confirm the file, the recipient, the cost and the password. Copy the password and send it to the recipient yourself, by text message for example, not by email.
- VitalSend emails the link. Without a recipient, your app shows you the link to share.
If your agent can reach the recipient another way, over Telegram or Slack for example, it can send the password itself while VitalSend emails the link. Your confirmation says so, and you have nothing to copy. The agent then sees the password, never the link.
These dialogs go to you, not to the model. The agent is told who it went to and when it expires, and, when it sends the password for you, the password. Nothing else.
What stays where
- The file is encrypted on your computer with the code vitalsend.eu runs in the browser. Only ciphertext leaves it.
- The link key, your login and the file id never go to the model. Nor does the password, unless the agent sends it for you.
- The password never reaches VitalSend. When VitalSend emails the link, its server handles the link key for that delivery; with a password, that key alone does not open the file.
- Your connection can send files and spend credits, nothing else. Revoke it on your account page.
Source and the full security model: github.com/vitalsend/mcp. Package: @vitalsend/mcp.

