Skip to main content
Glama

Related Servers

Alternatives to dbngin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that enables AI assistants to interact with and manage Windows systems, providing capabilities for file system operations, process management, system information retrieval, registry operations, service management, network diagnostics, and performance monitoring.
      7
      25 npm
      6
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to run PowerShell commands and manage Windows services without intrusive console windows, while also supporting remote execution via SSH and WinRM.
      20
      444 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to safely query and manage Windows services, processes, event logs, and system information, with write actions disabled by default.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to manage local development environments over MCP by starting, stopping, and restarting applications and processes, reading logs with cursors, and inspecting or freeing listening ports. Exposes a fixed set of id- and port-based tools, so the agent can operate registered processes without running arbitrary commands.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, diagnose, and manage a local Windows PC through the Model Context Protocol, with 97 tools for task management, cleanup, hardware and security checks, administration, networking, and shell helpers.
      179 PyPI
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: lifecycle actions (start/stop/restart), discovery (list_services), diagnostics (service_status), and log retrieval. The only mild overlap is list_services vs service_status since both surface running state, but descriptions clarify the former is for discovery and the latter for detailed per-service inspection.

    Naming Consistency4/5

    All names are snake_case and mostly follow a verb_noun pattern (list_services, start_service, stop_service, restart_service, get_logs). Minor deviations: service_status puts the noun first instead of a verb, and get_logs uses a different verb style than list_services for a read operation.

    Tool Count5/5

    Six tools is well-scoped for a local database service manager, covering exactly the discovery, lifecycle, and diagnostics operations an agent needs. No tool feels redundant or superfluous.

    Completeness4/5

    The surface covers the full service lifecycle (list, start, stop, restart, status, logs) with no dead ends for managing existing services. Minor gaps exist — no tool to create/register a new service or edit configuration/data paths, but core operational workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues