Despite my general distaste for shoehorned in AI features that no one wants, I have to admit that great language models have increased my productivity quite a bit. And I’m not just talking about cloud-based LLMs either. I’ve spent the last few months pairing my local models with open source tools, and these LLMs are surprisingly good at tackling OCR workflows, generating bookmark labels, organizing notes, and other bogus tasks.
That’s before including all the Model Context Protocol servers available for typical FOSS applications and platforms. In fact, I recently came across a couple of MCP servers designed for TrueNAS. Since it’s the distribution that powers the virtualized, local, and remote storage machines in my 3-2-1 backup workflow, I thought I’d try connecting. LLM with my TrueNAS instances. Now that I’ve been using LLM to control my NAS machines for a week, this setup is much safer and easier than you might think, as long as you keep some basic rules and don’t go overboard with your guidance.
Official TrueNAS MCP server is good enough for most users
Supports typical NAS operations without putting your data at risk
If you’re not sure how this MCP-based LLM setup works, let me quickly explain my setup. By itself, I can’t control it. TrueNAS via LLM instructions, and I would have to rely on their web UI or typical CLI scripts and commands to manage my storage groups. However, an MCP server turns this around by translating natural language instructions from my local LLM clients into API calls that my TrueNAS machines can understand. Therefore, I can issue typical commands to my LLMs and they will have no problem performing the specified operations on my NAS drives.
On paper, this sounds like a recipe for disaster, since a single vague command is all dumb, low-perimeter models need to wipe entire storage pools. But there are several ways to overcome this problem. I’ve mainly used the official MCP server released by TrueNAS and for the most part it’s pretty harmless. Most of the utilities available in this repository involve querying my TrueNAS configuration, and the only damage it can do is deleting my NAS shares, not their underlying data groups.
Additionally, I tend to use a 9B model (specifically Qwen 3.5) for my TrueNAS administration tasks, and this LLM has not misinterpreted my answers even after dozens of queries. I even tried deploying SMB apps and shares using Qwen 3.5 and as long as I use detailed prompts, it doesn’t pick random parameters when running API calls on my TrueNAS machines. I also disabled tools that can update my TrueNAS instances to further mitigate the chances of unrecoverable failures.
It’s also pretty easy to set up.
For reference, I’m using my RTX 3080 Ti to host LLM on LM Studioand although it runs on bloated Windows 11, I don’t have much trouble setting up the TrueNAS MCP server. First, I created a new API token for the MCP server within the My API Keys section in TrueNAS. Then I downloaded the truenas-mcp-windows-amd64.exe official’s file GitHub repository and moved it to the C:\Windows\System32 directory on my Windows 11 client. The GitHub repository has instructions on how to configure it for Claude Desktop, but the parameters for the mcp.json The file is more or less the same in LM Studio, and all I had to do was replace the thunder-ip-address and api key variables with local values:
{
"mcpServers": {
"truenas": {
"command": "truenas-mcp",
"args": (
"--truenas-url", "truenas-ip-address",
"--api-key", "api-key"
)
}
}
}
Remember to follow the correct JSON rules when configuring the MCP server.
Once I saved the file, the truenas-mcp server appeared in the Integrations section and I was able to enable it in my LLM chats.
The MCP server designed by spranab It’s another great repository.
Let me make it clear: the TrueNAS MCP server is a solid choice even for NAS lovers and hardcore data hoarders. But if you’re looking for something that can add even more features to the mix and you’re aware of the risks, you can check out additional GitHub repositories.
I have tried spranab TrueNAS MCP Server on a virtualized NAS that I use for my experiments and I like how it brings additional user and network management provisions to my LM Studio control center. Unlike the official MCP server, this one also avoids monopolizing the context window on my Qwen 3.5 LLM by exposing a single tool that houses other utilities. Credit where it’s due, the developer has also included additional provisions to ensure that LLMs don’t randomly execute destructive actions on their own. Setting it up was pretty easy and all I had to do was run installation npm -g truenas-mcp inside the command prompt, before copying the rest of the variables into the mcpServers header and change thunder to thunder-unofficial to avoid conflicts with your own MCP server.
But as a paranoid data hoarder who uses an external NAS just to ensure my backups and media files remain safe, I’ll stick with the official TrueNAS MCP server for now.
