ConnectWise RMM MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 Oct 2026.
ConnectWise RMM (Asio) MCP: offline agents, patch posture, and script runs across every client.
What the code does
We read the source, 20 h ago · rules 995398eba69f
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.
cacheFile := filepath.Join(c.cacheDir, c.cacheKey(path, params)+".json")
select {
case <-time.After(interval + jitter):
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Alternatives to ConnectWise RMM MCP
same job, measured the same wayMCP server for ConnectWise Automate RMM — computers, clients, alerts, and scripts.
MCP server for ConnectWise Automate RMM — computers, clients, alerts, and scripts.
Sync your ConnectWise Automate fleet to local SQLite and answer cross-client RMM questions offline.
Lossless archive and search for AI agent sessions across clients, exposed to agents over MCP.
A shared team wiki your coding agents read and write — across every repo and every MCP client.
Read-only Keeper MSP posture across every client, with history, a change feed and no path to a
Manage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent.
Every client's Jamf Pro in one CLI: find devices, check posture and patch status, audit policies.
ConnectWise RMM MCP — questions
Answers built from our own checks of this server.