Skip to main content
Glama
JUTZUGC

bososo-mcp

by JUTZUGC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to bososo-mcp

No user-submitted related servers found.

    Related Servers

    • openhoard by openhoard

      openhoardofficial

      openhoard
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, retrieve, and share files by meaning across connected storage, with permission-aware access control and an audit trail.
      Apache 2.0

    • A1 Google Drive MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      Enables AI apps to work with Google Drive in plain language, including searching, organizing, uploading, downloading, exporting, sharing, and commenting on files, with reversible trash and configurable access scopes.
      21
      69 npm
      MIT

    • sjtu-pan-mcp

      Mccount666
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to browse, search, and download files from Shanghai Jiao Tong University's cloud drive after QR-code login, without handling account passwords.
      8
      1
      MIT

    • gdrive-mcp-server

      devinxiong97
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible AI assistants to interact with a user's Google Drive, including listing, searching, reading, creating, updating, and deleting files, with authentication via Google OAuth.
      -
    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/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools map onto distinct, explicitly-numbered stages of a single workflow: bososo_search (step 1, keyword search returning tokens) and bososo_get_resource (step 2, token redemption). Their descriptions explicitly state the dependency (token must come from search), leaving no room for misselection.

    Naming Consistency5/5

    Both tools use the same bososo_ snake_case prefix with a clear action component (search, get_resource). The pattern is predictable and consistent.

    Tool Count4/5

    Two tools is on the lean side, but for a narrowly-scoped search-then-redeem pipeline each one earns its place with a distinct role. It is slightly under the typical 3-15 range but not a mismatch for the stated purpose.

    Completeness4/5

    The full end-to-end flow (find resources, exchange token for a savable share link) is covered with no dead ends. Minor gaps exist — no pagination, result filtering, or resource metadata/browsing — but agents can work around these via the search tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources