# mickaelkerjean/filestash [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/mickael-kerjean/filestash/tree/master/server/plugin/plg_handler_mcp  
**GitHub Stars:** 14831  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mickaelkerjean-filestash

## Description
Remote Storage Access: SFTP, S3, FTP, SMB, NFS, WebDAV, GIT, FTPS, gcloud, azure blob, sharepoint, etc.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What mickaelkerjean/filestash does

mickaelkerjean/filestash adds an MCP interface to Filestash's remote-storage access layer. It lets an AI agent work with storage destinations that have been configured in Filestash, instead of requiring a separate MCP server for every storage protocol.

Supported storage types include:

- FTP and FTPS
- SFTP
- S3
- WebDAV
- SMB
- NFS
- GIT
- gcloud
- Azure Blob
- SharePoint

The plugin is intended for agent-driven work against remote storage. Its role is to act as the interface between MCP clients and the storage connections available through Filestash.

## How it works

The plugin runs within the Filestash server and presents its remote-storage functionality through MCP. An MCP-compatible agent connects to the plugin and uses the exposed interface to perform work against a storage service configured in Filestash.

This architecture is useful when storage access is already centralized in Filestash. The agent does not need a direct, separately configured connection for each backend listed above; the relevant storage connection is selected from what Filestash has configured.

A demo endpoint is available at `https://demo.filestash.app/sse`. The `/sse` path indicates the demo uses a server-sent events connection for MCP communication.

## Setup and configuration

Run the MCP plugin as part of the Filestash server and configure the remote storage connection in Filestash. The plugin operates on those configured destinations, so the storage setup is a prerequisite for useful agent access.

For evaluation, the published demo endpoint can be used instead of setting up a local Filestash instance. The project also publishes a dedicated release note describing the MCP feature at `https://www.filestash.app/2025/04/01/mcp-feature/`.

The available storage backends depend on what has been configured in Filestash. A connection to one backend does not imply that the others are enabled.

## Tools and capabilities

The MCP interface is intended for remote-storage operations through Filestash. Its scope follows the configured backend rather than a single storage vendor or protocol.

Key capabilities include:

- Exposing Filestash storage access to MCP clients
- Working with FTP, FTPS, SFTP, S3, WebDAV, SMB, NFS, and GIT destinations
- Supporting gcloud, Azure Blob, and SharePoint storage connections
- Reusing storage configuration held by Filestash
- Connecting agents through the documented MCP endpoint

## Limitations and notes

This plugin depends on Filestash for the storage configuration and access layer. It is therefore best suited to deployments where the required remote storage is already configured in Filestash.

The server covers multiple remote-storage systems, but the actual destinations available to an agent depend on the Filestash instance. The public demo is useful for trying the MCP interface, while production use should account for the storage connections and access controls configured on the target Filestash deployment.

_Full upstream README: https://allmcps.com/mcp/mickaelkerjean-filestash/readme_