| name | filebrowser-mcp-connector |
| description | MCP connector for FileBrowser web file manager – enables AI-powered file operations, user management, and sharing through Claude |
| license | Apache 2.0 |
| tags | ["cloud","file-management","mcp","filebrowser"] |
| difficulty | beginner |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Filebrowser MCP Connector
Overview
This skill enables Claude to interact with Filebrowser through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Filebrowser's REST API, allowing natural language control of Filebrowser operations, intelligent automation, and AI-powered assistance for Filebrowser workflows.
When to Use This Skill
- File and directory operations via natural language
- User creation and permission management
- File sharing and link generation
- Bulk file operations and organization
- Custom command execution
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Filebrowser │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Filebrowser operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/resources, /api/users, /api/shares, /api/public, /api/settings
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "filebrowser-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Filebrowser resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/resources`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"filebrowser-mcp-connector": {
"command": "node",
"args": ["path/to/filebrowser-mcp-connector/index.js"],
"env": {
"FILEBROWSER_API_KEY": "your-api-key",
"FILEBROWSER_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Filebrowser API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Filebrowser API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Organize all documents by year, create download links for the latest reports, and clean up old temp files"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
