LabscoMCP early access ↗
nithiin7MCP SERVER

Remote File Server

Read the reports and spreadsheets on your SMB share from an assistant — without moving a file or granting write access.

by nithiin7 ↗Local Filesystem AccessCommunity

LABSCO SUMMARY

Network drives become answerable, and stay read-only.

The files stay where they are: it lists, searches and reads over SMB and parses the Office and PDF ones into text, with no write path at all — so pointing an assistant at the finance share is a question of what it can see, not what it can do.

What it is

A read-only bridge to an SMB/CIFS share: a Windows file server, a NAS, a Samba box. It exposes no write operations at all, and Office and PDF files are parsed into text on the way out.

What you get

  • Directory listings, file reads, search across the share, and metadata on any one file
  • Excel, Word, PowerPoint and PDF parsed into readable text, with the optional docs extras installed
  • Packet signing and encryption on by default, with encryption switchable off through configuration
  • Path traversal rejected before any SMB call is made
  • A denylist that never lists or reads .env files, *.key, *.pem, id_rsa or keystores
  • A subdirectory allowlist that locks the server to the folders the model actually needs
  • An audit log entry per call — operation, path, outcome — and never file contents

Requirements

Python 3.11 or newer and network reach to the share over SMB, named by SMB_HOST and SMB_SHARE. Share credentials are passed as environment variables and never appear in tool calls or chat history. Office and PDF parsing needs the optional docs extras.

Setup effort

Build from source — git clone https://github.com/nithiin7/remote-file-server-mcp.git /path/to/remote-file-server