Skip to main content
Glama
Josepavese

nido-mcp

by Josepavese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to nido-mcp

No user-submitted related servers found.

    Related Servers

    • proxmox-mcp

      ManciDRaffy
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to monitor and manage a Proxmox VE cluster, including cluster status, VM/container lifecycle, and node actions via MCP tools.
      8
      MIT

    • VPS-Guardian-MCP

      murzirius
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to safely monitor Linux VPS health, inspect Docker containers, retrieve service logs, and execute whitelisted recovery actions via MCP.
      31
      168 npm
      241 PyPI
      MIT

    • husk

      Hotragn
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate disposable Linux computers via MCP, providing tools for shell, file read/write, directory listing, and port exposure. It also supports browser automation and integration with any MCP-compatible client.
      Apache 2.0

    • smol-mcp

      smol-machines
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that lets AI agents manage virtual machines across local and cloud targets, with tools to create machines, run commands, transfer files, and clean up ephemeral instances via natural language.
      11
      3 npm
      Apache 2.0

    • Enterprise Infrastructure &

      Maneesh-Rajbhar
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to host system metrics (CPU, memory, disk), Docker container health/logs, and sandboxed log file analysis via MCP tools, enabling AI agents to monitor enterprise infrastructure safely.
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    The six tools map cleanly to distinct domains: events, VMs, templates, images, blueprints, and system operations. Minor potential overlap exists around image building, where nido_system build_image, nido_image pull, and nido_blueprint build could require an agent to reason about which layer is intended.

    Naming Consistency4/5

    All tools use a consistent nido_ namespace followed by a domain noun, making the set predictable. The only minor deviation is nido_events being plural while the other domain names are singular.

    Tool Count5/5

    Six tools is well within the appropriate range and each corresponds to a meaningful resource domain. The set is compact even though several tools expose many actions internally.

    Completeness4/5

    VM, image, system, and event operations are broadly covered, including lifecycle and port-forwarding actions. There are some minor gaps, such as template update/info operations and blueprint create/delete lifecycle operations, though resources may cover read-only inspection.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources