feiniunas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nas_statusA | 获取飞牛 NAS 的系统状态，包括主机名、运行时间、CPU 负载、内存使用、磁盘概况 |
| list_docker_containersA | 列出飞牛 NAS 上所有的 Docker 容器及其运行状态 |
| get_disk_infoA | 获取飞牛 NAS 的磁盘和存储详细信息，包括各挂载点的容量、已用、可用空间 |
| control_docker_containerB | 启动、停止或重启飞牛 NAS 上的 Docker 容器 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct concern: disk storage, system status, container listing, and container control. No overlap in purpose.
All tool names follow a clear verb_noun snake_case pattern (get_disk_info, get_nas_status, list_docker_containers, control_docker_container). Verbs are consistent with actions.
Four tools is well-scoped for a NAS management MCP, covering both monitoring and control without bloat.
Core NAS monitoring (disk, status) and Docker lifecycle (list, start/stop/restart) are covered. Minor gaps like container logs or network details could be added but are not critical.