Skip to main content
Glama
nuwainfo

ffl-mcp

Official
by nuwainfo

fflShareFiles

Share multiple local files by auto-zipping them into a single download link, with support for encryption, password protection, and download limits.

Instructions

Share multiple local files at once using ffl. ffl auto-zips them into a single download.

IMPORTANT: Always present the returned link so the user can click it to open in a browser. Do not display it as a plain unformatted URL — in some interfaces (such as Claude Dispatch) plain URLs are not auto-linked and will not be clickable.

Args: paths: List of local file paths to share together (auto-zipped by ffl) name: Custom download filename shown to recipient (e.g. 'release-v2.0.zip') e2ee: Enable end-to-end encryption (default: False) preview: Open recipient's browser directly in preview mode — shows a file list before downloading (default: False). Recommended when sharing multiple files so the recipient can inspect contents first. authUser: HTTP Basic Auth username to protect the link authPassword: HTTP Basic Auth password to protect the link maxDownloads: Stop serving after N downloads, P2P only (default: 1) timeoutSeconds: Stop serving after N seconds of inactivity, P2P only (default: 1800) waitLinkSeconds: Seconds to wait for link generation hookUrl: Custom webhook URL for events proxy: Proxy server URL (e.g. socks5://127.0.0.1:9050) qrInTerminal: Return ASCII QR code art for terminal display exclude: Exclude files matching glob or regex patterns, comma-separated recipientAuth: Recipient authentication mode — pickup, pubkey, pubkey+pickup, email pickupCode: Specific pickup code to use (default: auto-generated) recipientPublicKey: Path to recipient .fflpub public key file for pubkey auth recipientEmail: Recipient email(s) for OTP auth, comma-separated alias: Custom link alias instead of random UID (requires Standard+ account) receipt: Send email notification when recipient downloads receiptConfirm: Require recipient to confirm before download starts forceRelay: Disable direct WebRTC; route all traffic through tunnel upload: Upload to FFL server for async sharing — e.g. '1 day', '6 hours' (requires Standard+ account) resumeUpload: Resume an interrupted upload (default: False) preferredTunnel: Set preferred tunnel — cloudflare, ngrok, bore, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYes
nameNo
e2eeNo
authUserNo
authPasswordNo
maxDownloadsNo
timeoutSecondsNo
waitLinkSecondsNo
hookUrlNo
proxyNo
qrInTerminalNo
previewNo
excludeNo
recipientAuthNo
pickupCodeNo
recipientPublicKeyNo
recipientEmailNo
aliasNo
receiptNo
receiptConfirmNo
forceRelayNo
uploadNo
resumeUploadNo
preferredTunnelNo
portNo
inviteNo
pauseNo
enableReportingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It mentions sharing and returning a link, but lacks details on side effects, error handling, permissions, or rate limits. Important note about presenting URL is a usage instruction but not behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with purpose and important note, then structured parameter list. Some redundancy (e.g., default values repeated), but reasonable for the number of parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complex tool with 28 params, no annotations, and an output schema exists (so return values not needed). Input parameter descriptions are thorough, but missing behavioral warnings and explicit usage guidance. Still fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description fully compensates by explaining all 28 parameters with clear semantics, defaults, and usage notes. Each parameter gets a meaningful explanation beyond the schema's type-only information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'share', resource 'multiple local files', and action 'auto-zips them into a single download'. Distinguishes from siblings like fflShareFile (single file) and fflShareBase64 (base64).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies use for multiple files ('auto-zips') but does not explicitly state when to use this tool versus alternatives. No explicit 'when not to use' or comparison with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nuwainfo/ffl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server