Skip to main content
Glama

Related Servers

Alternatives to csa-skilljar

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to connect to a running MAGDA instance over stdio and access its native composition tools, resources, and resource templates, while providing instance discovery, fixed-instance connection, credential recovery, diagnostics, and compatibility checks.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.
      18
      42 npm
      5
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Gives an MCP client scoped, read-only-by-default access to your own Google account across Workspace apps and other Google APIs including Gmail, Calendar, Drive, Tasks, YouTube, Search Console, Analytics, and Photos. Runs locally over stdio with per-product write and separate destructive-tool opt-ins using your own OAuth client.
      45
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to interact with OpenCode 2.x/3.x servers through direct /api/... HTTP routing and ~85 tools spanning sessions, messages, files, config, providers, projects, input, TUI, and workflows. Runs as a zero-dependency, pure-JavaScript stdio bridge with no SDK or build step.
      85
      MIT

    TDQS

    A3.9/5.0

    Scored across 112 tools

    Disambiguation2/5

    Several tool pairs are genuinely confusable: delete_published_course performs identically to unpublish_published_course (its own description admits this), create_oauth_client and register_oauth_client both mint credentials with a load-bearing difference, and the v1/v2 progress tools (list_enrollments vs list_learner_progress) overlap. The descriptions work hard to disambiguate, but with 112 tools the misselection risk remains high.

    Naming Consistency4/5

    The core list_/get_/create_/update_/delete_ convention is strong and mostly predictable, with batch writes consistently plural and single-object deletes singular. Minor deviations exist but are documented: delete_published_course is deliberately misleading, get_signup_field_value takes a non-standard parameter name, and meta tools like demonstration_plan break the verb_noun pattern.

    Tool Count2/5

    112 tools is an extreme surface for any agent to navigate, even accounting for two API generations. The set includes deliberate duplicates (unpublish/delete published course, create/register OAuth client) and many read-only near-twins (list_labels/list_tags/list_course_labels) that could have been consolidated or split into separate servers by domain.

    Completeness3/5

    Core content lifecycle is well covered: courses, lessons, quizzes, question banks, groups, enrollments and published courses all have meaningful CRUD. But there are notable dead ends: no delete for courses or lessons, no webhook creation/update, and large v1 areas (promo codes, offers, ILT, paths) are read-only. Most gaps are documented as upstream API limits, but they will still cause agent failures when a user expects the full lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive