A
AIops-tools/TrueNAS-AIops
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"aiops-tools-truenas-aiops": {
"command": "uv",
"args": ["tool", "install", "truenas-aiops"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"aiops-tools-truenas-aiops": {
"command": "uv",
"args": ["tool", "install", "truenas-aiops"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio aiops-tools-truenas-aiops -- uv tool install truenas-aiops
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · AIops-tools/TrueNAS-AIops · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
uv tool install truenas-aiops
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uv tool install truenas-aiops. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
AIops-tools/TrueNAS-AIops;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# 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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/aiops-tools-truenas-aiops/)
- Source
- awesome · https://github.com/AIops-tools/TrueNAS-AIops
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.