
Qnap
io.github.marcelo-ochoaPublished by GitHub account marcelo-ochoav1.0.8Updated Oct 24, 2026
MCP server for QNAP NAS API
Overview
MCP server for QNAP NAS devices that lets an assistant connect to a NAS, monitor system health and storage, browse files and generate Markdown reports.
- What you can do
- Connect to a QNAP NAS with a host URL and admin credentials to obtain a session ID
- Generate a Markdown system report covering CPU, memory, disks and volumes
- List directory contents in a sorted tabular format
- Look up detailed information about a specific file
- Read disk and volume data as structured JSON resources for health and capacity monitoring
- When to use it
- Useful when you want an assistant to check a QNAP NAS's health, storage usage and file listings, or to produce a readable system report, without logging into the NAS web interface yourself.
- Requirements
- Runs as a local stdio process, typically via npx or a Docker image. Needs network access to the NAS URL and an admin username and password, supplied either through the connect tool or the QNAP_USER and QNAP_PASSWORD environment variables; the host can be passed as a startup argument for automatic connection.
Installation
In SourceWeft
- Open Qnap in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
QNAP MCP Server
An MCP server implementation for QNAP NAS devices, providing tools to monitor system status, manage files, and generate reports.
Tools
qnap-connect: Connect to a QNAP NAS and obtain a session ID.host: The QNAP NAS URL (e.g.,http://10.1.1.241:8080).username: Your admin username.password: Your admin password.
qnap-report: Generate a comprehensive Markdown system report including CPU, memory, powered bytoontables for disks and volumes. Perfect for both human reading and AI analysis.qnap-dir: List the contents of a directory in a professional tabular format, automatically sorted by modification date.path: The path to list (e.g.,/Public).
qnap-file-info: Get detailed information about a specific file.path: The directory path.filename: The name of the file.
Resources
The server exposes QNAP system components as MCP Resources, providing structured JSON data for monitoring:
- Disks:
qnap://[host]:[port]/disk/[disk-id]- Real-time disk health, model, serial, and temperature.
- Volumes:
qnap://[host]:[port]/volume/[volume-id]- Detailed storage usage, capacity, and volume names.
These resources allow AI models to monitor NAS health and storage levels without manually calling reporting tools.
Configuration
Environment Variables
The server can use environment variables and startup arguments for automatic connection:
QNAP_USER: QNAP admin username.QNAP_PASSWORD: QNAP admin password.
Startup Arguments
host: (Optional) URL of the QNAP NAS (e.g.,http://10.1.1.241:8080).
If the host and environment variables are provided, the server will attempt to connect automatically at startup.
Usage with Claude Desktop
Add the following to your claude_desktop_config.json:
using docker image
Development
Demos
See Demos for usage examples with Claude Desktop, Gemini CLI, and Antigravity Code Editor.
Docker
Building the container:
Running the container:
Change Log
See Change Log for the history of changes.
📜 License
This project is licensed under the Apache License, Version 2.0 for new contributions, with existing code under MIT - see the LICENSE file for details.
Source: src/qnap/README.md at commit bd2ce8f
Tools
0Version history
1- v1.0.8LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.