Skip to main content
Glama

Related Servers

Alternatives to infra-tak-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to administer a self-hosted AI control plane for users, organizations, subscriptions, API keys, model providers, and service health, with local-first model routing and cloud failover.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to manage a self-hosted RPort fleet by listing and inspecting connected devices, opening and closing SSH tunnels, and executing commands through RPort agents.
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables ERPNext management, file operations, read-only database access, and ERPNext API integration through a standardized MCP server.
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server that exposes Podman host management as tools, allowing natural language control of containers, images, volumes, networks, and pods. Includes an administrative console with safety profiles for gated access.
      18
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted Linux server control integration that lets remote MCP clients authenticate through persistent OAuth and invoke file, patch, command, terminal, Git, and image tools. Clients can also subscribe to targeted, signed event notifications for experimental event-driven workflows.
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation3/5

    The domain-prefixed tools mostly target distinct resources, but marketplace_call is a generic escape hatch that explicitly supports deploy/start/stop/restart/uninstall, directly overlapping marketplace_deploy, marketplace_control, and marketplace_uninstall. nodered_deploy_flows vs nodered_add_flow also sit close together (replace vs append the flow document). An agent could reasonably pick the wrong tool for marketplace operations.

    Naming Consistency4/5

    Strong, predictable snake_case with domain prefixes (marketplace_*, nodered_*, mediamtx_*, docker_*, tak_*). Two outliers lack a prefix (stack_health, advertise_ready_streams), which is a minor deviation but still readable.

    Tool Count4/5

    19 tools is on the heavy side but justified by spanning five subsystems (marketplace, Node-RED, MediaMTX, Docker, TAK). The count is slightly inflated by the redundant marketplace_call umbrella overlapping three dedicated marketplace tools.

    Completeness4/5

    Covers lifecycle across its domains: marketplace list/call/deploy/control/uninstall, Node-RED flows and palette, MediaMTX listing, Docker listing/logs, and TAK video publish/advertise. Minor gaps exist (no Docker container start/stop or MediaMTX path mutation), but core workflows are reachable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues