MCP Tools DirectoryAbout this integration
Read your TacticalRMM fleet; run commands only after per-command human approval.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.1.0
- Package
- trmm-mcp
- Last compatibility test
- Not independently tested
Connect your agent
trmm-mcpPublisher README and pyproject manifest were reviewed from hash-pinned captures. No TacticalRMM instance, credential, command, package, or remote endpoint was accessed; command mode is high-impact and requires separate operational authorization and safeguards.
Capabilities: Read TacticalRMM agents, checks, alerts, processes, services, patches, scripts, and audit data, Produce fleet diagnostics and reports, In configured execution modes, run commands or scripts and control managed systems
Connected profiles
Additional details
io.github.shin2344234/trmm-mcp
Source ↗ · Checked 2026-09-171.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17TRMM_API_URL, TRMM_READONLY_API_KEY
Source ↗ · Checked 2026-09-17trmm-mcp
Source ↗ · Checked 2026-09-191.1.0
Source ↗ · Checked 2026-09-19The publisher explicitly documents a command mode for unattended execution and a local stdio launch path. Default readonly and approval-gated elevate modes are also documented; none was run.
Source ↗ · Checked 2026-09-19The server uses separately provisioned TacticalRMM API keys; remote HTTP mode additionally requires a bearer token and certificate, while the reviewed catalog connection remains local stdio.
Source ↗ · Checked 2026-09-19On the server host, an MCP client launches /opt/trmm-mcp/run.sh readonly over stdio; swapping the mode to command enables the documented unattended execution behavior.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19