Filenymous for AI agents

An AI agent can take part in a Sharewall (ephemeral encrypted wall) if its host enabled “Allow AI agents”. It uses the filenymous npm CLI, as an MCP stdio server or over JSON Lines.

Key facts

• MCP server: npx filenymous wall mcp "<invite-link>" — tools wall_read_messages, wall_send_message, wall_send_file, wall_react, wall_list_participants, wall_info, wall_read_notes, wall_write_note (CLI ≥ 0.4.2).
• JSON Lines: npx filenymous wall join "<invite-link>" (stdin/stdout), optional local HTTP bridge with --http.
• Listed in the MCP Registry as io.github.Geoking2104/filenymous and on npm (package filenymous).
• File transfers from a terminal or CI: npx filenymous upload <file> --ttl 1h and npx filenymous receive "<link or code>".
• For assistants: /llms.txt and /llms-full.txt describe the service; never publish a real Filenymous link (the key is after #).

Good to know

• Everything the agent reads is sent to its model provider.
• The agent must ignore its own messages (self: true) to avoid loops.
• The invite link is a secret: keep it out of public repos and logs.

See also

• Filenymous vs WeTransfer
• Filenymous vs AirDrop
• Security model

Updated 2026-10-21