Skip to main content
Glama
stickafile-mcp

stickafile-mcp

by gitkvn

Related Servers

Alternatives to stickafile-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables 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
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely transfer files between machines via encrypted, expiring share links, with tools for upload, download, status checks, and link management.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents upload text, images, and files to Pixeldrain and download files back to the local machine, returning shareable file or album URLs. Supports optional API key binding so uploads belong to a user's account.
      73
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to move files of any size to and from wherever they need to go: uploading into a browser you're already signed in to (no size cap), driving a headless or attached Chrome/Brave over CDP, transferring to cloud storage via rclone, and copying to drives, NAS mounts, iCloud Drive folders or the clipboard. Exposes these as MCP tools for Claude Code, Codex and similar agents, plus a matching CLI.
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.