Mcp Smb Server

What is Mcp Smb Server?

Mcp Smb Server is a runtime file-access gateway for AI agents using the Model Context Protocol (MCP). It allows agents to access SMB/CIFS shares or local filesystem paths while preserving native filesystem permission enforcement—if the underlying system cannot read a file, the agent cannot read it either.

How to use Mcp Smb Server?

Build the server from source with Go 1.24+, then run it in SMB mode via environment variables (e.g., MCP_MODE=smb, SMB_ADDR, SMB_SHARE) or in local mode with a config file (e.g., ./mcp-smb-server --config config.yaml). Configuration is process-level and loaded once at startup.

Key features of Mcp Smb Server

• Exposes files only at access time (no indexing)
• Relies on native SMB/OS permission enforcement
• Supports SMB/CIFS and local filesystem backends
• Communicates over stdio (VS Code/agent friendly)
• Provides list_directory and read_file MCP tools

Use cases of Mcp Smb Server

• Let AI agents browse and read files from SMB shares without duplicating data
• Give agents controlled local filesystem access with OS permission enforcement
• Integrate file access into MCP-aware environments (e.g., VS Code, custom agents)
• Enable runtime file access without indexing, sync, or embedding pipelines

FAQ from Mcp Smb Server

How does Mcp Smb Server differ from file indexing solutions?

It does not sync, index, embed, or copy files. All access happens at runtime, relying on native filesystem or SMB permissions—no permission bypass or policy reimplementation.

What are the runtime requirements?

Go 1.24 or later. For SMB mode, access to an SMB/CIFS server. For local mode, appropriate filesystem permissions.

Where does file data reside?

Data stays on the original filesystem or SMB share. The server never stores or duplicates it.

What MCP tools does it provide?

list_directory (lists files at a path) and read_file (reads a bounded portion, default 8 KB).

What transports and authentication does it use?

Communication over stdio only. SMB authentication is handled by the SMB server (credentials set via environment variables, not stored in config files).