Synapse RMCP runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 10 Sep 2026.
Host, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.
We read the source, 9 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/install.js
const install = spawnSync(process.execPath, [installer], { stdio: "inherit" });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
if std::path::Path::new("/.dockerenv").exists()
credentials_file="$HOME/.aws/credentials"
-v /var/run/docker.sock:/var/run/docker.sock \
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add synapse -- npx -y @dinglebear/synapse
{
"mcpServers": {
"synapse": {
"args": [
"-y",
"@dinglebear/synapse"
],
"command": "npx"
}
}
}
[mcp_servers.synapse]
command = "npx"
args = ["-y", "@dinglebear/synapse"]
{
"mcpServers": {
"synapse": {
"args": [
"-y",
"@dinglebear/synapse"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"synapse": {
"args": [
"-y",
"@dinglebear/synapse"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
SYNAPSE_HOME (Optional Synapse appdata directory.), SYNAPSE_HOSTS_CONFIG (Inline host topology as a JSON array.), SYNAPSE_CONFIG_FILE (Path to a host configuration file.), SYNAPSE_RMCP_VERSION (Optional GitHub release tag override for the downloaded Synapse binary.), SYNAPSE_RMCP_REPO (Optional GitHub owner/repo override for release asset downloads.), SYNAPSE_RMCP_RELEASE_BASE_URL (Optional release download base URL override.), RUST_LOG (Tracing filter for Synapse logs.).
The author declared them in the registry entry; get the values from the project itself.
Rust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations.
Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.
Arcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP.
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
Pare Docker ג€” Structured Docker operations (ps, images, logs, build, compose) as typed JSON.
Python MCP server for AWS CLI inspection and operations
Rust MCP server and CLI for Arcane Docker and container management.
Answers built from our own checks of this server.