Skip to main content
Glama

Related Servers

Alternatives to nvidia-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      It enables MCP-compatible AI clients to run local device, filesystem, shell, PowerShell, Git, browser, HTTP, clipboard and application actions on a Windows PC and a paired Android phone, with session-based device routing. Sensitive operations are gated behind configurable one-use approvals and recorded in a local SQLite audit.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Local MCP server for observing and controlling an authorized Android device over USB using ADB and scrcpy, providing screen capture, UI automation, app inspection, logcat, and evidence recording.
      29
      41 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A locally-run, read-only MCP server that lets an LLM client diagnose a self-hosted *arr media stack by aggregating across Sonarr, Radarr, Prowlarr, qBittorrent, Tdarr, and Profilarr.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A safety-oriented Model Context Protocol (MCP) server for inspecting, controlling, diagnosing, and selectively administering a Home Assistant instance.
      MIT

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource+action, and the settings family (kodi_settings vs kodi_addon_settings vs kodi_set_setting vs kodi_set_addon_setting) is carefully differentiated by object and read/write. A few pairs like kodi_backup_file/kodi_backups and kodi_patch_file/kodi_set_setting require close reading, but boundaries are largely clear.

    Naming Consistency4/5

    All names use lowercase snake_case with consistent shield_/kodi_ namespace prefixes, and verbs are predictable (read, patch, restore, set, preview, apply). Some entries are noun-only (kodi_status, kodi_addons, kodi_logs) rather than verb_noun, a minor deviation but still readable and grouped.

    Tool Count3/5

    25 tools is heavy for what is essentially a Shield/Kodi inspection-and-safe-edit server, and the surface sits right at the borderline where maintenance and selection cost grow. The extensive safety-related variants (backup/patch/restore, manager layout trio) are arguably each justified, but a leaner surface would reduce cognitive load.

    Completeness4/5

    The surface covers device lifecycle and diagnostics, logs, file read/backup/patch/restore round-trips, settings and add-on settings, and optional Manager layout staging/apply/rebuild, giving strong lifecycle coverage. Only minor gaps remain, such as no dedicated file-delete or broader addon-management operations, which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues