Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Archiware MCP

No user-submitted related servers found.

    Related Servers

    • drumfire-proxmox-mcp

      Drumfire01
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude to manage a Proxmox cluster through chat: inventory, power control, configuration changes, VM/container creation and cloning, snapshots, network/firewall/cluster visibility, guest command execution, and file writes via the QEMU Guest Agent.
      22 npm
      MIT

    • ai-ssh-mcp

      guozhiwei01
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language SSH server management via Claude Code, allowing users to read logs, check services, run commands, and transfer files across multiple servers.
      6
      MIT

    • ppdm-mcp-server

      Moodswing9
      A
      license
      B
      quality
      B
      maintenance
      Exposes Dell EMC PowerProtect Data Manager and NetWorker backup infrastructure as Claude Code tools for querying, monitoring, and controlling backup operations.
      32
      470 npm
      MIT

    • 1Panel MCP Server V1

      ffdkj
      A
      license
      D
      quality
      C
      maintenance
      Enables AI clients such as Claude Desktop, Cursor, and Claude Code to administer a 1Panel v1.x server through 257 MCP tools covering containers and images, apps and runtimes, files, backups, databases, websites, firewall, and monitoring. Supports both stdio and token-authenticated HTTP/SSE transports for local or remote access.
      257
      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

    B3.1/5.0

    Scored across 84 tools

    Disambiguation3/5

    Most tools have distinct purposes, but several clusters overlap heavily: restore vs restore_version vs restore_volume vs restore_archive vs catalog_restore, jobs vs job_history vs job, and status vs health vs container_status. The long descriptions usually disambiguate them, but an agent must read carefully and may still misselect among the restore and job-history tools.

    Naming Consistency4/5

    Almost all names use snake_case with recognizable domain prefixes (plan_, job_, library_, tape_, catalog_, container_), and read-only tools tend to be nouns while mutating tools use verb_noun. Generic outliers like rest, nsdchat, and pack_status slightly break the pattern but are minor.

    Tool Count2/5

    84 tools is far beyond the typical manageable range, even for a broad backup-appliance domain. Many clusters (restore variants, library workflow steps, job inspection, catalogue search/restore) could be consolidated, and the sheer surface area increases selection cost and accidental misuse.

    Completeness4/5

    Coverage is extensive: plans/tasks/jobs, tape library operations, restore previews and execution, catalogue search/pack/restore, container maintenance, mail diagnostics, governance, and health checks are all present. Minor gaps exist, such as P5 mail settings being read-only and single-file restores for unindexed jobs returning GUI steps rather than executing via P5.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources