Skip to main content
Glama

Related Servers

Alternatives to GWL MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables querying RetroAchievements data — user profiles, unlocks, game progress, game and achievement details, leaderboards, comments, tickets, and site feeds — through 15 read-only, token-efficient tools that cover all documented Web API endpoints over stdio or Streamable HTTP.
      15
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the full public ListenBrainz API, exposing 37 tools for listens, stats, playlists, radio, social, and cover art over stdio.
      37
      1
      BSD Zero Clause
    • A
      license
      B
      quality
      B
      maintenance
      Exposes 30 tools to manage Redmine resources (issues, projects, users, time entries, wiki pages, news, files, roles) via the REST API using stdio transport.
      34
      306 npm
      7
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Connects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables ZenTao user administration, including token retrieval, user queries, and user creation/update/delete, over stdio or Streamable HTTP transports.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables interaction with Canvas LMS through its REST API, allowing users to manage courses, assignments, submissions, grades, modules, discussions, enrollments, users, and account-level reports. Supports student, instructor, and account administrator workflows with stdio and streamable HTTP transports.
      21 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools have sharply distinct purposes, and the descriptions explicitly disambiguate dangerous near-pairs (gwl_get_document vs gwl_get_document_by_id, gwl_list_documents vs gwl_list_my_documents, gwl_ping vs gwl_get_me vs gwl_get_permissions). The remaining fuzziness is mild: gwl_list_my_classes, gwl_list_my_orgs and gwl_list_joinable_classes all partly answer "what can I access", and the three tag tools plus gwl_search overlap slightly on discovery.

    Naming Consistency5/5

    Every tool uses the same gwl_ prefix plus snake_case verb_noun construction (get/list/create/update/delete/restore/add/remove/set/join/cancel/review/mark/search/suggest), with no camelCase or stylistic drift. Only gwl_ping lacks a verb, which is a trivial and conventional exception.

    Tool Count3/5

    36 tools is heavy, but the surface genuinely spans several domains (identity/permissions, orgs & groups, join-request workflow, blacklist, documents + revisions, tags, search, notifications). It is still borderline oversized: the document and membership clusters each run ~12 tools and offer obvious consolidation room (e.g. separate list_my_documents / list_documents / list_trash variants).

    Completeness3/5

    Document lifecycle is excellent (create/read/update/soft-delete/restore, revisions and revision restore, trash), and the join-request and blacklist workflows are fully closed-loop. However there are notable holes: no way to list or remove members of a class, no leave_class, and folders are read-only (list_folders only) despite folder_id being required for create_document — agents will dead-end needing a folder they cannot create or manage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues