Hosting

Remote Filestash MCP Gateway; the documented demo uses a read-only WebDAV storage. The gateway can also be enabled on a self-hosted Filestash instance.

Transport

Server-Sent Events (SSE) upstream, bridged to local stdio by mcp-remote

Endpoint

https://demo.filestash.app/sse

Authentication

The official demo opens the Filestash sign-in flow. A self-hosted instance uses the storage and authorization configured in Filestash; no separate MCP token is documented.

Requirements

• Node.js with npx to run mcp-remote.
• For a self-hosted deployment, an installed Filestash instance with the MCP Gateway feature enabled and at least one authorized storage connection.

Setup steps

1. For a demonstration connection, configure the MCP client to run `npx` with args [`mcp-remote`, `https://demo.filestash.app/sse`] using stdio.
2. Start or reload the MCP server. Complete the browser sign-in flow when the client opens it, then inspect tools/list.
3. The official demo uses a read-only WebDAV storage. A harmless check is to list the root directory; the Filestash guide shows the `ls` tool for this check.
4. For your own Filestash deployment, open `/admin/settings`, enable the MCP Gateway feature, and connect the storage you intend to expose. Use the MCP Gateway address configured for your instance; the documentation gives the demo endpoint but does not specify a universal self-hosted URL pattern.
5. Restrict accessible storage and permissions before connecting an agent. The official guide recommends chroot and authorization rules to limit access and deletion.

The official guide demonstrates the `ls` tool and says the gateway exposes operations for the authenticated storage, but it does not publish a complete protocol tools/list inventory. Inspect tools/list after connecting; available operations depend on the connected storage and permissions.

• ls

  List the contents of a path in the connected remote storage, as shown in Filestash's official MCP Gateway guide.

  01

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Connection and tool behavior were not independently tested for this catalog record.
• The published demo endpoint is a test instance backed by read-only WebDAV storage; production use should connect to a properly permissioned Filestash instance.
• The official guide shows a Claude Code stdio bridge and a ChatGPT developer-mode example, but does not provide a universal self-hosted endpoint URL pattern or a complete tools/list schema.
• The gateway exposes actions on the storage configured in Filestash. Restrict permissions because file operations may include deletion or modification depending on the connected backend.

• official mcp gateway documentation

  Describes MCP Gateway feature configuration, the demo SSE endpoint, authentication flow, the read-only WebDAV demo backend, an example `ls` call, and storage-permission safety guidance.

• official installation documentation

  Documents supported self-hosted installation methods, including the standalone Linux binary and Docker image.

• official repository

  Filestash's official repository links to filestash.app and documents its storage management platform; the repository showed approximately 14.8k stars when checked.

• official product logo

  Logo asset linked from the official Filestash website. The SVG contains a white line mark; it was rasterized with an opaque dark tile for legibility on both light and dark directory surfaces. Selection tier A: product logo.

• discovery directory

  The October 17 research shortlist included Filestash as a high-star MCP candidate; directory ranking was used only for discovery, not as setup evidence.

• official or maintainer tool reference

  Official guide describes one generic filesystem operation gateway, with operations and data access determined by configured storage backend.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.