omni-fs-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@omni-fs-mcp list files in /home/user"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Omni-FS MCP Server
An MCP server that provides unified access to multiple file systems simultaneously through OpenDAL.
Installation
pip install omni-fs-mcpRelated MCP server: MinIO Model-Context Protocol (MCP) Server
Quick Start
Single Backend
# Local filesystem
omni-fs-mcp "fs://"
# S3
omni-fs-mcp --transport http "s3://bucket?region=us-east-1&access_key_id=xxx&secret_access_key=yyy"
# WebDAV
omni-fs-mcp "webdav://server.com/path?username=user&password=pass"
# Memory (testing)
omni-fs-mcp "memory://"Multi-Backend with Config File
Create backends.json:
{
"backends": [
{
"name": "local",
"url": "fs://",
"description": "Local filesystem",
"default": true
},
{
"name": "s3-prod",
"url": "s3://bucket?region=us-east-1&access_key_id=...",
"description": "Production S3"
}
]
}Run with config:
# Stdio (default)
omni-fs-mcp backends.json
# HTTP
omni-fs-mcp --transport http --config backends.json --port 8080Usage
Command Options
omni-fs-mcp [OPTIONS] [URL_OR_CONFIG]
Options:
--config FILE JSON configuration file
--transport TYPE stdio (default) or http
--port PORT HTTP port (default: 8000)
--host HOST HTTP host (default: localhost)Available Tools
File Operations:
list_files(path, backend=None)- List files and directoriesread_file(path, backend=None)- Read file contentswrite_file(path, content, backend=None)- Write to filecopy_file(src, dst, src_backend=None, dst_backend=None)- Copy filesrename_file(src, dst, backend=None)- Rename/move filescreate_dir(path, backend=None)- Create directorystat_file(path, backend=None)- Get file metadata
Backend Management:
register_backend(name, url, ...)- Add new backendlist_backends()- Show all backendsset_default_backend(name)- Set default backendremove_backend(name)- Remove backendcheck_backend_health(backend=None)- Check connectivity
Supported Backends
Type | URL Example |
Local |
|
S3 |
|
WebDAV |
|
Memory |
|
FTP |
|
HTTP |
|
Examples
Cross-Backend Copy
# Backup to S3
copy_file("/local/file.txt", "/backup/file.txt",
src_backend="local", dst_backend="s3-backup")Runtime Backend Management
# Add temporary backend
register_backend("temp", "memory://", description="Temp storage")
# Use it
write_file("/test.txt", "content", backend="temp")Development
git clone <repo>
cd omni-fs-mcp
uv sync
# Run locally
uv run omni-fs-mcp "memory://"License
MIT
Available Tools
13 toolscheck_backend_healthB
Check the health status of backends by attempting basic operations.
Args:
backend: Specific backend to check (checks all if not specified)
Returns:
Dictionary mapping backend names to their health status (True/False)
Inputs: backend. Returns: object
copy_fileB
Copy a file between backends or within the same backend.
Args:
src: Source file path
dst: Destination file path
src_backend: Source backend name (uses default if not specified)
dst_backend: Destination backend name (uses default if not specified)
Returns:
Success message
Inputs: src (required), dst (required), src_backend, dst_backend. Returns: result
create_dirB
Create a directory on the specified backend.
Args:
path: Directory path to create
backend: Backend name to use (uses default backend if not specified)
Returns:
Success message
Inputs: path (required), backend. Returns: result
get_backend_statsA
Get statistics and information about the backend manager.
Returns:
Dictionary with total backends, default backend, healthy backends count, etc.
Inputs: no named parameters. Returns: object
list_backendsA
List all registered backends with their configurations and status.
Returns:
List of backend information including name, URL, description,
readonly status, default status, and health status
Inputs: no named parameters. Returns: result
list_filesB
List files and directories in the specified path.
Args:
path: The directory path to list (default: "/")
backend: Backend name to use (uses default backend if not specified)
Returns:
List of entries with their metadata
Inputs: path, backend. Returns: result
read_fileC
Read file contents from the specified backend.
Args:
path: File path to read
backend: Backend name to use (uses default backend if not specified)
Returns:
File contents as string
Inputs: path (required), backend. Returns: result
register_backendA
Register a new backend with the given configuration.
Args:
name: Unique identifier for the backend (alphanumeric, hyphens, underscores only)
url: Backend connection URL (e.g., "fs:///", "s3://bucket", "memory:///")
description: Human-readable description of the backend
readonly: Whether this backend should be treated as read-only
timeout: Connection timeout in seconds
retry_attempts: Number of retry attempts for failed operations
set_as_default: Whether to set this as the default backend
validate_connection: Whether to validate the connection during registration
Returns:
Success or failure message
Inputs: name (required), url (required), description, readonly, +4 more. Returns: result
remove_backendA
Remove a backend from the manager.
Args:
name: Name of the backend to remove
force: Force removal even if it's the default backend
Returns:
Success message
Inputs: name (required), force. Returns: result
rename_fileB
Rename or move a file within a backend.
Args:
src: Source file path
dst: Destination file path
backend: Backend name to use (uses default backend if not specified)
Returns:
Success message
Inputs: src (required), dst (required), backend. Returns: result
set_default_backendB
Set the default backend for operations when no backend is specified.
Args:
name: Name of the backend to set as default
Returns:
Success message
Inputs: name (required). Returns: result
stat_fileA
Get metadata/statistics for a file or directory.
Args:
path: Path to get statistics for
backend: Backend name to use (uses default backend if not specified)
Returns:
File metadata object
Inputs: path (required), backend.
write_fileA
Write content to a file on the specified backend.
Args:
path: File path to write to
content: Content to write to the file
backend: Backend name to use (uses default backend if not specified)
Returns:
Success message
Inputs: path (required), content (required), backend. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a distinct operation: file reading, writing, copying, renaming, listing, directory creation, and backend management. No overlap or ambiguity.
All tools follow a consistent snake_case verb_noun pattern (e.g., write_file, list_backends), making them predictable and easy to understand.
With 13 tools, the server covers both file operations and backend management comprehensively without being bloated.
The file operations cover most CRUD but are missing a delete file tool, which is a significant gap for a file system server. Backend management seems complete.
Maintenance
Related MCP Connectors
Browse, upload, download, and share files in your S3-compatible buckets with delegated roles.
Transfer and sync files between 19 cloud storages (Yandex, Google, VK, Telegram, S3)
Browse, upload, download, copy, move and share files in your own S3-compatible buckets.
Persistent file storage for AI agents via MCP and curl. Upload, download, and version files.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides seamless access to multiple storage services including S3, Azure Blob Storage, and Google Cloud Storage through Apache OpenDAL™.335Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides a standardized way to interact with MinIO object storage, allowing access to text files, binary files, and bucket contents while supporting operations like listing buckets/objects, retrieving objects, and uploading files.6MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides unified access to multiple cloud object storage services (Huawei OBS, Alibaba OSS, AWS S3, MinIO) enabling AI assistants to list, search, retrieve, and manage unstructured data across different storage providers.-
- FlicenseAqualityNot gradedmaintenanceEnables unified access to both structured databases (PostgreSQL, MySQL, SQLite, etc.) and unstructured object storage (AWS S3, Alibaba OSS, Huawei OBS, etc.) through a single interface.7-