truenas-aiops
Related Servers
Alternatives to truenas-aiops
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for TrueNAS Scale that enables AI assistants to manage storage pools, datasets, apps, VMs, snapshots, and more via the native WebSocket API.5948 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants to manage TrueNAS Scale Custom Apps using natural language commands, with tools for deploying, managing, and monitoring Docker Compose applications.7MIT
- AlicenseAqualityBmaintenanceAn MCP server for TrueNAS that lets users manage ZFS pools, datasets, shares, snapshots, VMs, alerts, and network configuration through natural language, using a single hierarchical tool exposing 278 actions.1461 npm1MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server for TrueNAS SCALE that enables read-first management of storage, system, sharing, and virtualization resources with per-user API key authentication, and optional write operations.2MIT
- AlicenseBqualityBmaintenanceAn MCP server that turns your TrueNAS instance into tools, letting you manage disks, pools, apps, VMs, shares, and more from any MCP client.29MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude Desktop and other MCP clients to interact with TrueNAS Core systems through the TrueNAS API, supporting user management, storage operations, sharing, and snapshot creation.20147 PyPI34MIT
TDQS
Scored across 25 tools
Pool-related reads overlap heavily: pool_get, pool_status, pool_capacity, and pool_health_rca all describe per-pool health/capacity/scan info, and overview vs pool_health_rca vs alert_and_capacity_rca present competing 'triage' summaries. Descriptions differentiate them somewhat (RCA tools do worst-first flagging, overview is a summary), but an agent could easily misselect among them. The write/undo tools and snapshot/dataset/service tools are otherwise distinct.
The set follows a mostly predictable noun_verb snake_case convention (dataset_list, pool_get, snapshot_create, service_restart, undo_apply). A few outliers like 'overview' and 'smart_test_results' deviate slightly, but nothing is jarring or mixed-convention. Readable and largely consistent.
25 tools sits at the heavy end of the scale, and several reads (overview, pool_health_rca, alert_and_capacity_rca, pool_get, pool_status, pool_capacity) feel like redundant coverage of the same triage surface. The set is workable but not tight; some consolidation would earn each tool's place more clearly.
Coverage spans pools, datasets, snapshots, disks, SMART, alerts, services, replication, cloudsync, and system info, plus a governed write/undo mechanism. Gaps exist — no dataset delete/update (explicitly out of scope), no pool create/destroy, no share (SMB/NFS) or user management, no snapshot rollback — but these are workable around the core storage-admin workflows.