Save-To-NAS

Save-To-NAS MCP is an MCP server that saves files and folders directly to a local NAS over NFS. It streamlines data transfers by handling discovery, mounting, and copying in a single, repeatable workflow so you can move data to NAS storage quickly and reliably.

How to use

You run the Save-To-NAS MCP server through an MCP client, configure it with the NAS address, and then use the provided tools to transfer files to the NAS shares. The server discovers NAS exports, mounts shares if needed, and copies your data while preserving attributes.

Key capabilities you’ll use:

• Save files or folders to a NAS share
• List available NAS shares and see which are mounted
• Automatic mounting of unmounted shares (requires sudo) and data transfer with attribute preservation.

How to install

Prerequisites you need before installing:
- Node.js and npm (Node 14+ is a common baseline; check your environment requirements)
- Access to your NAS over the network via NFS
- sudo privileges to mount unmounted shares
- A working MCP client to manage MCP servers and configurations

Install via the MCP workflow (recommended):

mcp install save-to-nas-mcp
mcp edit save-to-nas --env "NAS_IP=192.168.1.100"
mcp add save-to-nas --profile your-profile  # Add to a profile

Install via npm (global):

npm install -g save-to-nas-mcp

Install from source (optional if you want to run locally from repository):

git clone https://github.com/danielrosehill/Save-To-NAS-MCP.git
cd Save-To-NAS-MCP
npm install

Configuration

Configure the MCP server with environment variables. The following variables are used to connect to your NAS and determine where to mount shares.

NAS_IP=192.168.1.100
NAS_MOUNT_BASE=/mnt/nas
NAS_VOLUME_PREFIX=/volume1

MCP server configuration examples

There are two equivalent ways to start the server within your MCP setup. Use either the npx-based invocation or a direct global command, depending on how you installed the package.

{
  "mcpServers": {
    "save-to-nas": {
      "command": "npx",
      "args": ["-y", "save-to-nas-mcp"],
      "env": {
        "NAS_IP": "192.168.1.100"
      }
    }
  }
}

If you installed the package globally, you can configure it like this instead.

{
  "mcpServers": {
    "save-to-nas": {
      "command": "save-to-nas-mcp",
      "env": {
        "NAS_IP": "192.168.1.100"
      }
    }
  }
}

Tools and usage details

The MCP provides two core tools for NAS transfers.

- save_to_nas: Save a file or folder to a NAS share
  Parameters:
  - source: Path to the local file or folder (required)
  - share: NAS share name (required)
  - destination_subfolder: Optional subfolder inside the share

- list_nas_shares: List available NFS shares on the NAS and show mounted status
  Parameters:
  - filter: Optional share name filter

Notes on NAS and mounting

What happens when you trigger a transfer:

1. The server queries the NAS to discover available NFS exports
2. It checks whether the target share is already mounted locally
3. If not mounted, it attempts to mount via NFS (requires sudo)
4. It transfers your data to the destination, preserving file attributes and metadata.

Requirements and license

You need a Linux system with NFS client tools installed (for example nfs-common on Ubuntu/Debian), network access to the NAS, configured NFS exports on the NAS, and sudo privileges to mount shares.

License: MIT

Available tools

save_to_nas

Save a local file or folder to a NAS share. Requires source path, target share name, and optional destination subfolder.

list_nas_shares

List available NAS NFS shares and show which ones are mounted locally.