Storage your agents can use.
Give Claude, Cursor or your own agents a key. They send files, keep files, and fetch what others send them. Hosted in Germany, so files stay in the EU.
Share links
Agents upload deliverables and hand back a link, with expiry, password and email delivery.
Persistent drive
A private file space agents can read and write across sessions, until you delete it.
Scoped keys
Read-only or read-write keys, revocable any time. Keys can never touch billing or your account.
CLI
Requires Node 20+. Create a key on your account page, then:
npm install -g @sehihi/cli # or prefix any command with: npx @sehihi/cli
sehihi login --key sehihi_… --url https://your-sehihi-domain
# Share links
sehihi send report.pdf video.mp4 --expires 7 --password "correct horse"
sehihi download https://your-sehihi-domain/t/<id> --out ./inbox
# Persistent drive
sehihi put ./build.zip releases/
sehihi ls releases/
sehihi get releases/build.zip ./
sehihi share releases/build.zip --to [email protected]Add --json to any command for machine-readable output. SEHIHI_API_KEY and SEHIHI_URL work instead of login, which suits CI and sandboxes.
MCP server
Claude Desktop, Cursor and other MCP clients: add this to the client’s MCP configuration.
{
"mcpServers": {
"sehihi": {
"command": "npx",
"args": [
"-y",
"@sehihi/cli",
"mcp"
],
"env": {
"SEHIHI_API_KEY": "sehihi_…",
"SEHIHI_URL": "https://your-sehihi-domain"
}
}
}
}Claude Code:
claude mcp add sehihi --env SEHIHI_API_KEY=sehihi_… --env SEHIHI_URL=https://your-sehihi-domain -- npx -y @sehihi/cli mcpTools: sehihi_send_files, sehihi_list_transfers, sehihi_delete_transfer, sehihi_drive_list, sehihi_drive_upload, sehihi_drive_download, sehihi_drive_delete, sehihi_drive_share, sehihi_drive_move, sehihi_update_transfer, sehihi_download_share, sehihi_whoami.
Ask a person for files: sehihi_request_create returns an upload link, sehihi_request_wait waits for the upload, sehihi_received_download fetches it. Also sehihi_request_list, sehihi_request_close, sehihi_received_list, sehihi_received_delete and sehihi_activity (who downloaded what, and from where).
HTTP API
Every CLI command is a plain HTTP call with Authorization: Bearer sehihi_…. Uploads are chunked into 8 MB parts with a SHA-256 hash each, so they resume and are verified end to end.
curl -H "Authorization: Bearer $SEHIHI_API_KEY" https://your-sehihi-domain/api/drive
curl -H "Authorization: Bearer $SEHIHI_API_KEY" -o build.zip https://your-sehihi-domain/api/drive/files/releases/build.zip