Tomas Svoboda QNAP recently announced support for MCP (Model Context Protocol) for its NAS systems and introduced MCP Assistant (Beta), which allows users to control common NAS operations using natural language. This innovation represents a shift from mere data storage to intelligent device control — the NAS becomes an active entity that understands and executes user commands.
The MCP protocol comes from an initiative to connect large-scale models (LLMs, like Claude, GPT types) with external systems — allowing them to not only respond but also intervene in the environment, trigger actions, call APIs, read structured data, etc. QNAP integrates it so that models can actually “act” within the NAS — create folders, manage users, monitor the system, operate on storage, or read structured data.
What is MCP (Model Context Protocol)?
MCP is an open protocol designed to enable models (LLMs) to “understand the context” of their environment and invoke actions — that is, not just generate text, but actively influence systems. It is a bridge between “intelligence” and concrete operations. The model receives a command in natural language (e.g. “create a folder for backups”), MCP translates it into a concrete action (API call, script run) and executes it on the target system (in our case, a NAS device).
Importantly, the protocol supports:
- multi-turn conversations (the model remembers the context and relationships between commands)
- access to various tools and APIs
- authentication and management of access legitimacy (tokens, keys)
What is MCP Assistant at QNAP?
MCP Assistant is an application component (in beta) from QNAP that acts as a "deployed MCP host" inside a NAS environment. It allows you to receive commands from a model (e.g. from Claude Desktop, Copilot, or other clients) and execute them on the NAS.
In practice, it works like this:
- The user enters a command in natural language
- The model translates the command into a specific API call via the MCP
- MCP Assistant on the NAS will perform the necessary steps
- The result is returned to the user.
MCP Assistant supports various NAS management tasks, including:
- shared folder management
- user and group management
- system monitoring
- storage operations
- working with files
- integration with the Qsirch search engine
How to set up and use MCP Assistant
- Update your NAS to QTS/QuTS hero 5.2 or later.
- V App Center, activate the Beta Program and install "MCP Assistant".
- Create a key, set permissions, and download the client.
- Edit the client configuration file (Claude, Copilot, etc.).
- Run the client and test the commands.
That's a brief overview. If you need the exact steps to set up Claude on macOS, then proceed as follows.
1. Create credentials
- Go to QTS or QuTS hero on your NAS device and launch the app MCP Assistant.
- On card Credentials click the button Create.
- Enter the login key name and select a method Key.
- Select a specific NAS user and specify which features they will have access to (for example, file manager, users, storage).
- If you do not want the model to make changes, you can activate the mode Read-only.
- Download the generated access package (ZIP file) which contains everything needed to connect Claude Desktop to the NAS. For the purposes of this guide, the package for Mac with M1 chips and newer.
Gallery
2. Installing the MCP server on your computer
- Unzip the downloaded ZIP file on your computer.
- Make sure you see the file in the unzipped folder qmcp (executable MCP server) and configuration files.
- When macOS it is possible that the application will prevent running when the system is first started – see below.
Security changes macOS a Windows when starting MCP Server
When you first start the MCP Server in the environment macOS A security warning may appear that prevents it from running immediately. In this case, click "Done" and proceed to Apple Menu → System Settings → Security & Privacy → Security. Find the information here.macio blocked file qmcp and click Allow anyway. We recommend that you only allow executable files from trusted and verified sources to minireduced the risk of system compromise.
3. Editing the Claude Desktop configuration file
- Open the file
claude_desktop_config.json(located in the Claude Desktop configuration folder). - Find or add a section
"mcp_servers". - In this section, insert the path to the executable file qmcp from the previous step. For example:
"mcp_servers": { "qnap_mcp": { "path": "/Users/uzivatel/Downloads/qnap-mcp/qmcp", "args": ["--start"], "env": {} } }
After setup, you need to restart the application and possibly turn it off completely in the Activity Monitor. If you have done everything according to the instructions, the NAS will connect to the Claude desktop application and you can start entering tasks.
In a system Windows It is possible that an antivirus or firewall is blocking the MCP Server from starting. In this case, verify that the application is not blocked and add it to the exceptions if necessary. If you need to reload the previous configuration (for example, in the Claude Desktop application), you must completely close it: v macOS via the Force Quit feature or in Activity Monitor, in Windows using Task Manager and End Task. After restarting, we recommend testing functionality using commands such as: "Can you connect to my QNAP NAS?" or "View storage status." In case of an error, check the application interface, which will usually provide more detailed information.mace.
Examples of use
- "Do I have a highway vignette stored on my NAS?"
- "What applications are installed on the NAS?"
- "Show the 5 largest folders in the system."
- "Does the NAS have enough power to play 4K videos?"
Gallery
Future direction and the contribution of MCP
QNAP is already actively working on further expanding the functionality of MCP and plans to integrate with a wider range of third-party tools. In the future, we can expect support for additional artificial intelligence platforms, greater compatibility with various NAS models, and, above all, deeper integration with automation tools. Development will also focus on enterprise use - i.e. multi-device management, scalability, central access rights management, and advanced activity logging.
A key element of the development remains the integration with the n8n tool, which serves as a visual tool for creating automation flows without the need for programming. By connecting MCP to n8n, artificial intelligence can directly trigger complex workflows based on simple natural commands. This opens up completely new possibilities not only for ordinary users, but also for IT administrators who are looking for an efficient and secure way to automate tasks across the corporate environment. It is also expected that feedback from the community during the beta phase will significantly influence the final form of the system – whether in terms of stability, functionality, or user interface.
MCP brings a whole new way to interact with your NAS – moving from traditional clicks and scripting to conversational control that is natural, intuitive and understandable even for less technically savvy users. By combining natural language, artificial intelligence and direct connection to system functions, your NAS becomes a truly intelligent data and storage manager. It can respond to requests in real time, analyze data, optimize operations and simplify daily tasks.
Although MCP opens up new possibilities in the field of NAS system management, it is important to emphasize secure settings, management of access rights and strict control over what actions the models perform. Given that artificial intelligence gains direct access to data and system tools, it is essential to implement sufficient security measures and regularly review the set permissions. Only in this way can the full potential of the new technology be utilized without the risk of compromising sensitive data or system integrity.
