Skip to main content
Glama
heindewilde

Yungle

by heindewilde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yungle

No user-submitted related servers found.

    Related Servers

    • VFS DMS ChatGPT Plugin

      mergi72
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.
      MIT

    • tamlil-mcp

      Steven17D
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to finished meeting transcripts for AI assistants like Claude Code or Codex, enabling them to answer questions or draft summaries based on the transcriptions.
      4
      3
      Apache 2.0

    • Sprinklr MCP Server

      daiict218
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.
      4 npm
      ISC

    • mattermost-mcp

      shin6949
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding tools to search and read a user's Mattermost channels and DMs using their own account, allowing AI to answer questions about team conversations with read-only access.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct object or action: transfers (list/get/downloads), collections (list/get/files/folders), guests, contacts, upload requests, and the link-resolution pair. The only near-overlap, get_download_links vs download_files, is cleanly separated by output (signed URLs vs files on disk) and the descriptions make that explicit.

    Naming Consistency5/5

    Every tool follows a clean snake_case verb_noun pattern (list_*, get_*, download_files). The convention is uniform and predictable across all 14 tools.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and each one maps to a distinct resource or operation in the file-transfer domain. Nothing feels padded or redundant.

    Completeness4/5

    The read/inspection and download surface is thorough, covering accounts, transfers, collections, folders, guests, contacts, upload requests and link resolution. However, the surface is entirely read-only: no tools to create transfers/collections, invite guests, add contacts, or manage upload requests, so the write lifecycle is absent (possibly by design).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources