TacticalRMM runs on your own machine — the client starts it, so there is no endpoint to ping. 103 installs a week from pypi. Last commit 8 Sep 2026.
Read your TacticalRMM fleet; run commands only after per-command human approval.
What the code does
We read the source, 2 d 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.
out = subprocess.run(
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.
Connect this server
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 trmm-mcp -e 'TRMM_API_URL=<TRMM_API_URL>' -e 'TRMM_READONLY_API_KEY=<TRMM_READONLY_API_KEY>' -- uvx trmm-mcp{
"mcpServers": {
"trmm-mcp": {
"command": "uvx",
"args": [
"trmm-mcp"
],
"env": {
"TRMM_API_URL": "<TRMM_API_URL>",
"TRMM_READONLY_API_KEY": "<TRMM_READONLY_API_KEY>"
}
}
}
}[mcp_servers.trmm-mcp]
command = "uvx"
args = ["trmm-mcp"]
env = { TRMM_API_URL = "<TRMM_API_URL>", TRMM_READONLY_API_KEY = "<TRMM_READONLY_API_KEY>" }{
"mcpServers": {
"trmm-mcp": {
"command": "uvx",
"args": [
"trmm-mcp"
],
"env": {
"TRMM_API_URL": "<TRMM_API_URL>",
"TRMM_READONLY_API_KEY": "<TRMM_READONLY_API_KEY>"
}
}
}
}{
"servers": {
"trmm-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"trmm-mcp"
],
"env": {
"TRMM_API_URL": "<TRMM_API_URL>",
"TRMM_READONLY_API_KEY": "<TRMM_READONLY_API_KEY>"
}
}
}
}Put your own values in place of
<TRMM_API_URL> (Base URL of your TacticalRMM backend, e.g. https://api.example.com), <TRMM_READONLY_API_KEY> (TacticalRMM API key bound to a read-only role. Used for all reads).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
TRMM_COMMAND_API_KEY (TacticalRMM API key permitted to execute. Only needed for elevate or command mode, and only used after an approval is granted), TRMM_MCP_MODE (readonly (default, 20 read tools), elevate (adds 8 execution tools, each requiring out-of-band human approval), or command (execution with no gate)).
Alternatives to TacticalRMM
same job, measured the same wayRun shell commands on remote computers with optional per-command approval, using only curl and bash.
Preventive human-approval write-gate for AI agents: writes commit only after a human approves.
Read your Comment Scraper exports of Reddit and Hacker News threads. Local and read-only.
Set up human approval for your AI agents' tool calls.
Your agent posts, schedules, queues and threads posts on X, with a human approval queue.
Amazon PPC data, P&L and inventory for AI assistants; changes only after your approval.
Run commands on your computers remotely with TRIGGERcmd.
Jobs matched to your resume, tailored resumes, and applications hirly sends only after you confirm.
TacticalRMM — questions
Answers built from our own checks of this server.