| name | seafile-mcp-connector |
| description | MCP connector for Seafile file hosting – enables AI-powered file synchronization, library management, and collaboration through Claude |
| license | AGPL |
| tags | ["cloud","file-management","mcp","seafile","sync"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Seafile MCP Connector
Overview
This skill enables Claude to interact with Seafile through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Seafile's REST API, allowing natural language control of Seafile operations, intelligent automation, and AI-powered assistance for Seafile workflows.
When to Use This Skill
- Library creation and file management via AI
- Share link generation and management
- File history and version management
- Group and department organization
- Wiki and knowledge base management
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Seafile │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Seafile operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api2/repos/, /api2/repos/:id/file/, /api/v2.1/share-links/, /api/v2.1/groups/
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: "seafile-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Seafile 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}/api2/repos/`, {
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": {
"seafile-mcp-connector": {
"command": "node",
"args": ["path/to/seafile-mcp-connector/index.js"],
"env": {
"SEAFILE_API_KEY": "your-api-key",
"SEAFILE_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 Seafile 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 Seafile API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a new library for the Q2 reports, upload the files, and share a read-only link with stakeholders"
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.
