Skip to main content
Glama
jgordini

UAB Research Computing Documentation MCP Server

by jgordini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to UAB Research Computing Documentation MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-slurm

      tejasvinu
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage SLURM HPC clusters via SSH. Supports job submission, resource monitoring, queue management, and file operations.
      2 npm
      4
      -

    • Unsloth AI Documentation MCP

      jdanas
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides tools to search and retrieve Unsloth AI documentation, including quickstart guides, supported models, and installation instructions. It enables AI assistants to query documentation content in real-time through an MCP-compatible interface.
      1
      -

    • Jamf Docs MCP Server

      GET-Technology-Inc
      A
      license
      A
      quality
      A
      maintenance
      Provides AI assistants with direct access to Jamf official documentation, enabling them to answer Jamf-related questions by searching, retrieving articles, and browsing product documentation.
      6
      858 npm
      3
      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.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_cheaha_quick_start provides cluster-specific onboarding, get_documentation_page retrieves full page content, get_support_info offers contact details, list_documentation_sections shows the documentation structure, and search_documentation enables content discovery. The descriptions reinforce these distinct roles, making tool selection unambiguous for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_, list_, search_) with clear, descriptive names that align with their functions. The naming convention is uniform across all five tools, using snake_case consistently without any deviations or mixed styles, making the set predictable and easy to navigate.

    Tool Count5/5

    With 5 tools, this server is well-scoped for its documentation-focused purpose, covering key user needs: onboarding (get_cheaha_quick_start), navigation (list_documentation_sections, search_documentation), content access (get_documentation_page), and support (get_support_info). Each tool earns its place without redundancy, and the count is neither too thin nor overwhelming for the domain.

    Completeness5/5

    The tool surface provides complete coverage for a documentation server, addressing the full user journey: discovering documentation (search, list), accessing content (get page), getting started (quick start), and seeking help (support info). There are no obvious gaps—agents can effectively browse, retrieve, and navigate the documentation without dead ends or missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources