stickafile-mcp
Related Servers
Alternatives to stickafile-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables AI assistants to upload files and folders to a Pshare instance and generate share links, with support for optional password, TTL, and chunked uploads for large files.1-

YAFL MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely transfer files between machines via encrypted, expiring share links, with tools for upload, download, status checks, and link management.MIT- AlicenseNot gradedqualityBmaintenanceEnables moving artifacts from ChatGPT/Codex sandboxes to remote server storage via host-native file parameters, streaming large files without Base64 or model-context overhead.MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to list, upload, download, and delete files on named static sites served by a private home lab, with token scopes controlling read-only or destructive access.Apache 2.0

@putput/mcpofficial
FlicenseNot gradedqualityDmaintenanceFile uploads for AI agents. Upload, list, and manage files from AI coding assistants like Claude, Cursor, Windsurf, and VS Code Copilot with no signup required.1-- FlicenseAqualityBmaintenanceEnables AI agents and users to upload and download files via MCP, generating shareable links and identifier codes. Files are automatically deleted after 24 hours.9-
TDQS
Scored across 2 tools
push uploads a file and returns a link, while list_portals enumerates available portals; these are clearly distinct resource+action pairs with no overlap. The descriptions even clarify the dependency relationship between them without creating ambiguity.
Both names use lowercase snake_case, but 'push' is a bare verb while 'list_portals' follows the verb_noun convention. The deviation is minor and both remain readable and predictable in style.
Two tools is thin even for a focused file-sharing server; the primary action (push) plus one helper leaves no room for adjacent operations. It is defensible for a narrowly scoped uploader, but sits at the borderline of feeling under-provisioned.
The core upload-to-link workflow and portal discovery are covered, but there is no way to list files already in a portal, check upload status, delete/revoke a previously shared file, or manage portals beyond listing them. These are notable gaps for a file-sharing lifecycle.