A Model Context Protocol (MCP) server for Synology NAS devices. Enables AI assistants to manage files and downloads through secure authentication and
Synology mcp server connects Synology to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for Synology NAS devices. Enables AI assistants to manage files and downloads through secure authentication and session management.
A Model Context Protocol (MCP) server for Synology NAS devices. Enables AI assistants to manage files and downloads through secure authentication and session management.
Once connected, the assistant can call these 3 tools directly:
Architecture — The Architecture tool exposed by this serverDeploy — 1. mcp-proxy is installed automatically when you build the HTTP image — it lives in requirements-http.txt and the provided compose file sets theSecurity — mcp-proxy does not provide server-side authentication. Anything that can reach the HTTP endpoint can call every tool. Mitigations:Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before the server will start you need to supply 6 environment variables: SYNOLOGY_URL, SYNOLOGY_USERNAME, SYNOLOGY_PASSWORD, AUTO_LOGIN, ENABLE_XIAOZHI, XIAOZHI_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.
Cloud and DevOps servers put infrastructure on speaking terms with your assistant, so "why is this broken?" is answered from real state rather than a generic checklist. Synology sits in that group, and the shape of its toolset — Architecture, Deploy, Security — tells you what it is really for. Worth comparing against the other cloud devops servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Architecture | The Architecture tool exposed by this server. |
| Deploy | 1. mcp-proxy is installed automatically when you build the HTTP image — it lives in requirements-http.txt and the provided compose file sets the INSTALL_HTTP=true build arg (it is not in the default stdio/Xiaozhi image). |
| Security | mcp-proxy does **not** provide server-side authentication. Anything that can reach the HTTP endpoint can call every tool. Mitigations: |
{
"mcpServers": {
"synology": {
"command": "docker-compose",
"args": [
"-f", "/path/to/your/mcp-server-synology/docker-compose.yml",
"run", "--rm", "synology-mcp"
],
"cwd": "/path/to/your/mcp-server-synology"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SYNOLOGY_URL | Endpoint or connection string the server talks to. | Yes |
| SYNOLOGY_USERNAME | Configuration value read at startup. | Optional |
| SYNOLOGY_PASSWORD | Configuration value read at startup. | Optional |
| AUTO_LOGIN | Configuration value read at startup. | Optional |
| ENABLE_XIAOZHI | Configuration value read at startup. | Optional |
| XIAOZHI_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.