Technical preview. The package is ready for local testing; the public connection and directory listings are pending launch.
Works with compatible MCP clients. Directory availability depends on each platform's review.
You
Create a FilesUp share called Final delivery, send these files and give me the link.
Final deliveryFiles + message + persistent link
One link, many sends
Create a share once. Add files and messages later, at the same address.
Your account. Your control.
Authorize access in FilesUp. Disconnect the assistant whenever you want.
Files with a time limit
File content expires after ten days. History and thumbnails remain in your share.
Copy. Paste. Connect.
Let your assistant handle the setup.
Copy this prompt into Codex or Claude Code. Your assistant downloads the plugin and configures the connection. You sign in to FilesUp and authorize access in your browser.
Use an assistant with access to your computer. Depending on the client, you may need to open a new session or confirm installation.
Add this remote server URL and use the client's browser sign-in flow:
https://api.filesup.app/mcp
File upload requires a client that can read local files and send HTTP requests, such as Codex or Claude Code.
Know what you authorize.
The assistant can read your shares, create shares and publish messages and file sends, and upload files using your quota. Anyone with an active group link can see what you publish there. Connection does not replace your FilesUp login or grant access to another account.
Never paste passwords, login codes or tokens into chat. Authorization happens in FilesUp, and you can revoke it in your account menu.
Help us improve FilesUp
With your permission, we use Google Analytics to understand visits and usage. We do not send content, contacts or link tokens. Learn more