A
AIops-tools/TrueNAS-AIops
SECURITY.md ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项（本地服务器用 command + args，示例见 客户端接法） - 重启客户端
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"aiops-tools-truenas-aiops": {
"command": "uv",
"args": ["tool", "install", "truenas-aiops"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"aiops-tools-truenas-aiops": {
"command": "uv",
"args": ["tool", "install", "truenas-aiops"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio aiops-tools-truenas-aiops -- uv tool install truenas-aiops
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · AIops-tools/TrueNAS-AIops · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 1 ★ · 23 个来源 · mcp
- 安装
uv tool install truenas-aiops
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uv tool install truenas-aiops。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
AIops-tools/TrueNAS-AIops；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# TrueNAS AIops
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by iXsystems or the TrueNAS project. "TrueNAS" is a trademark of its owner. MIT licensed.
AI-powered TrueNAS SCALE storage operations with a built-in governance
harness — unified audit log, token/runaway budget guard, undo-token
recording, and descriptive risk tiers. Speaks both TrueNAS APIs: REST v2.0
and the JSON-RPC/WebSocket API that replaces it in TrueNAS 26.
> Verification status: live-verified against a real TrueNAS SCALE 25.04.2.1
> appliance over both transports, including a full write → audit → undo →
> verified-restore loop. Coverage is listed endpoint by endpoint — and so are
> the gaps — in docs/VERIFICATION.md. Read it rather
> than reading "verified" as "everything".
## Supported TrueNAS versions — and which API you are speaking
truenas-aiops speaks both TrueNAS APIs and picks the one that will still
exist:
| TrueNAS version | REST API v2.0 | JSON-RPC over WebSocket | what this tool does |
| ≤ 25.10.0 | supported | — | REST |
| 25.04 – 25.10.x | deprecated (every call raises an appliance alert) | already served at /api/current | WebSocket (auto) |
| 26 and newer | removed | required | WebSocket |
Set transport: per target in config.yaml:
yaml
targets:
name: nas1
host: nas1.example.com
transport: auto # default — probe /api/current, prefer WebSocket
# transport: websocket # pin the API that survives TrueNAS 26
# transport: rest # pin REST while migrating
auto probes /api/current with a cheap HTTP upgrade (no credential spent). If
the appliance offers it, the tool uses it; otherwise it falls back to REST,
which is still correct on 25.10 and older.
iXsystems documents that upgrading to TrueNAS 26 revokes existing API keys —
so expect to mint a new one after the upgrade. We have not reproduced this
ourselves; it is reported here from the upstream release notes, not from a
verified upgrade. Treat it as a caution, not a measurement.
truenas-aiops doctor tells you which transport the connection actually used,
reads the server version, and — on REST — says plainly whether REST is
supported, deprecated, or gone. If the version cannot be parsed it reports
UNKNOWN, never a clean bill of health it cannot justify.
## What works
CLI (truenas-aiops ...): init, overview, system, pool list/get/status/scrub-status/capacity/scrub-start, dataset list/get/create, diagnose pool-health/alerts, snapshot list/create/delete, disk list/smart, alert list, service list/restart, replication list/cloudsync, secret set/list/rm/migrate/rotate-password, doctor, mcp.
MCP server (truenas-aiops mcp or truenas-aiops-mcp): 25 tools (19 read, 6 write), every one wrapped with the bundled @governedtool harness.
Encrypted credentials: the TrueNAS API key lives in an encrypted store ~/.truenas-aiops/secrets.enc (Fernet + scrypt) — never plaintext on disk. Unlock with a master password from TRUENASAIOPSMASTERPASSWORD (MCP/CI) or an interactive prompt (CLI).
Reversibility: snapshotcreate records an inverse snapshotdelete undo descriptor. The irreversible snapshotdelete (high risk) captures the snapshot's BEFORE state for the audit record and declares no undo.
AI-powered TrueNAS SCALE storage operations with a built-in governance
harness — unified audit log, token/runaway budget guard, undo-token
recording, and descriptive risk tiers. Speaks both TrueNAS APIs: REST v2.0
and the JSON-RPC/WebSocket API that replaces it in TrueNAS 26.
> Verification status: live-verified against a real TrueNAS SCALE 25.04.2.1
> appliance over both transports, including a full write → audit → undo →
> verified-restore loop. Coverage is listed endpoint by endpoint — and so are
> the gaps — in docs/VERIFICATION.md. Read it rather
> than reading "verified" as "everything".
## Supported TrueNAS versions — and which API you are speaking
truenas-aiops speaks both TrueNAS APIs and picks the one that will still
exist:
| TrueNAS version | REST API v2.0 | JSON-RPC over WebSocket | what this tool does |
| ≤ 25.10.0 | supported | — | REST |
| 25.04 – 25.10.x | deprecated (every call raises an appliance alert) | already served at /api/current | WebSocket (auto) |
| 26 and newer | removed | required | WebSocket |
Set transport: per target in config.yaml:
yaml
targets:
name: nas1
host: nas1.example.com
transport: auto # default — probe /api/current, prefer WebSocket
# transport: websocket # pin the API that survives TrueNAS 26
# transport: rest # pin REST while migrating
auto probes /api/current with a cheap HTTP upgrade (no credential spent). If
the appliance offers it, the tool uses it; otherwise it falls back to REST,
which is still correct on 25.10 and older.
iXsystems documents that upgrading to TrueNAS 26 revokes existing API keys —
so expect to mint a new one after the upgrade. We have not reproduced this
ourselves; it is reported here from the upstream release notes, not from a
verified upgrade. Treat it as a caution, not a measurement.
truenas-aiops doctor tells you which transport the connection actually used,
reads the server version, and — on REST — says plainly whether REST is
supported, deprecated, or gone. If the version cannot be parsed it reports
UNKNOWN, never a clean bill of health it cannot justify.
## What works
CLI (truenas-aiops ...): init, overview, system, pool list/get/status/scrub-status/capacity/scrub-start, dataset list/get/create, diagnose pool-health/alerts, snapshot list/create/delete, disk list/smart, alert list, service list/restart, replication list/cloudsync, secret set/list/rm/migrate/rotate-password, doctor, mcp.
MCP server (truenas-aiops mcp or truenas-aiops-mcp): 25 tools (19 read, 6 write), every one wrapped with the bundled @governedtool harness.
Encrypted credentials: the TrueNAS API key lives in an encrypted store ~/.truenas-aiops/secrets.enc (Fernet + scrypt) — never plaintext on disk. Unlock with a master password from TRUENASAIOPSMASTERPASSWORD (MCP/CI) or an interactive prompt (CLI).
Reversibility: snapshotcreate records an inverse snapshotdelete undo descriptor. The irreversible snapshotdelete (high risk) captures the snapshot's BEFORE state for the audit record and declares no undo.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/aiops-tools-truenas-aiops/)
- 来源
- awesome · https://github.com/AIops-tools/TrueNAS-AIops
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md（我们只核文件存在，未核内容）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。