synology-chat-mcp
Integrates with self-hosted Synology Chat instances, allowing users to list joined channels and DMs, find users, read recent posts and files, send text messages, and upload local files.
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., "@synology-chat-mcp list my unread channels and show recent posts in the busiest one"
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.
synology-chat-mcp
MCP server for Synology Chat. Works with any self-hosted Synology Chat instance: list channels, read recent posts, find users, send messages and upload files from any MCP client (Claude Desktop, Claude Code, Hermes, ...).
It logs in as a normal DSM user through the Synology Web API, so it sees exactly what that user sees in Chat (channels and DMs), no bot or webhook setup needed.
Tools
Tool | What it does |
| Joined channels and DMs (id, name, type, members, unread) |
| Find users by partial username |
| Most recent messages/files in a channel or DM |
| 1:1 DM channel id for a user, or |
| Post a text message |
| Upload a local file, optionally followed by a message |
Related MCP server: Direxio Local MCP
Configuration
All config comes from environment variables, set them in your MCP client config:
Variable | Required | Example |
| yes |
|
| yes | DSM username |
| yes | DSM password |
| no |
|
A URL without scheme means https, without port it uses 443 (https) or 80 (http).
Install
Needs uv. No clone required, uvx runs it straight from GitHub.
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"synology-chat": {
"command": "uvx",
"args": ["--from", "git+https://github.com/Louis-Lastella/synology-chat-mcp", "synology-chat-mcp"],
"env": {
"SYNOLOGY_CHAT_URL": "https://chat.example.com",
"SYNOLOGY_CHAT_USER": "your-username",
"SYNOLOGY_CHAT_PASS": "your-password"
}
}
}
}Claude Code:
claude mcp add synology-chat \
-e SYNOLOGY_CHAT_URL=https://chat.example.com \
-e SYNOLOGY_CHAT_USER=your-username \
-e SYNOLOGY_CHAT_PASS=your-password \
-- uvx --from git+https://github.com/Louis-Lastella/synology-chat-mcp synology-chat-mcpHermes (~/.hermes/config.yaml):
mcp_servers:
synology-chat:
command: uvx
args: [--from, git+https://github.com/Louis-Lastella/synology-chat-mcp, synology-chat-mcp]
env:
SYNOLOGY_CHAT_URL: https://chat.example.com
SYNOLOGY_CHAT_USER: your-username
SYNOLOGY_CHAT_PASS: your-passwordFrom a local clone instead: git clone, uv sync, then use uv with args --directory /path/to/synology-chat-mcp run synology-chat-mcp.
Docker (no uv needed), image ghcr.io/louis-lastella/synology-chat-mcp:
{
"mcpServers": {
"synology-chat": {
"command": "docker",
"args": ["run", "-i", "--rm",
"-e", "SYNOLOGY_CHAT_URL", "-e", "SYNOLOGY_CHAT_USER", "-e", "SYNOLOGY_CHAT_PASS",
"ghcr.io/louis-lastella/synology-chat-mcp"],
"env": {
"SYNOLOGY_CHAT_URL": "https://chat.example.com",
"SYNOLOGY_CHAT_USER": "your-username",
"SYNOLOGY_CHAT_PASS": "your-password"
}
}
}
}Also listed in the official MCP Registry as io.github.Louis-Lastella/synology-chat-mcp.
Notes
Accounts with 2-factor authentication are not supported (the Web API wants a fresh OTP per login). Use an account without 2FA.
DMs show up with type
anonymous, that is Synology's name for 1:1 conversations.find_useronly matches theusername, not display names.Downloading attachments is not a tool yet. The session is available via
synology_chat_mcp._client().session; callGET /webapi/entry.cgi?api=SYNO.Chat.Post.File&method=get&version=2&post_id=<id>&_sid=<sid>with the headerX-SYNO-TOKEN: <session.syno_token>.
Development
uv sync
uv run python tests/test_parse_url.pyLicense
MIT
Available Tools
6 toolsdm_channel_for_userDm Channel For UserA
Find (or None if none exists yet) the 1:1 DM channel_id for a given user_id.
Inputs: user_id (required). Returns: result
find_userFind UserA
Find users by (partial, case-insensitive) username, e.g. 'smith'.
Inputs: name_query (required). Returns: result
get_recent_postsGet Recent PostsC
Read the most recent messages/files in a channel or DM.
Inputs: channel_id (required), limit. Returns: result
list_channelsList ChannelsA
List all joined chat channels/DMs with id, name, type, last_post_at.
Inputs: no named parameters. Returns: result
send_fileSend FileB
Upload a file to a channel/DM, optionally followed by a text message.
Inputs: file_path (required), channel_id (required), message. Returns: object
send_messageSend MessageC
Post a text message to a channel/DM.
Inputs: message (required), channel_id (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a clearly distinct operation: discovery (list_channels, find_user), reading (get_recent_posts), DM resolution (dm_channel_for_user), and sending (send_message, send_file). There is little risk of confusing send_message with send_file or get_recent_posts with list_channels.
Most tools use a predictable snake_case verb_noun pattern: list_channels, find_user, get_recent_posts, send_message, send_file. The one deviation is dm_channel_for_user, which is noun-oriented rather than verb-led, but it remains readable and semantically clear.
Six tools is well-scoped for a chat integration focused on discovery, reading, DM lookup, and sending. Each tool has a distinct and necessary role, with no obvious bloat.
The set covers the core chat lifecycle: list channels, find users, resolve DMs, read recent posts, and send messages or files. Minor gaps exist around message search, editing/deleting messages, or channel creation, but core workflows are covered.
Maintenance
Related MCP Connectors
Agent-to-agent messaging: directory, public lobby, DMs, channels, search. Stateless MCP + REST.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
WhatsApp (Web + Business API), SMS, contacts, and call records via 2Chat's MCP server.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Rocket.Chat instances through MCP protocol. Allows users to manage chat operations and integrate with Rocket.Chat servers using natural language commands.6-
- AlicenseBqualityDmaintenanceLocal MCP server for Direxio chat workflows enabling room search, messaging, and channel post management.615 npmMIT
- FlicenseAqualityCmaintenanceEnables reading channels and messages, finding users, and sending messages and files to bbw-chat.de (Synology Chat) from any MCP client.6-
- AlicenseNot gradedqualityCmaintenanceEnables agents to discover rooms, read conversations, register, create rooms, post messages, and reply through MCP or HTTP with bearer-token authentication.MIT