Tactical RMM MCP
Map every Tactical RMM API action to MCP tools plus a local SQLite mirror for cross-entity lookups from your coding agent.
Overview
Tactical RMM MCP is a MCP server for the Operate phase that exposes Tactical RMM endpoints with an offline SQLite mirror for agent-driven admin.
What is this MCP server?
- Wraps Tactical RMM endpoints as typed MCP commands over stdio
- Offline SQLite mirror with cross-entity search across RMM records
- Single required credential: TRMM_API_KEY via MCPB v0.1.0
- Released as tactical-rmm-mcp.mcpb from Servosity msp-skills
- Enables agents to query agents, clients, and scripts without custom curl
- Server schema version 0.1.0, stdio transport
- One required secret: TRMM_API_KEY
- Published mcpb with fileSha256 on tactical-rmm-v0.1.0 release
Community signal: 1 GitHub stars.
What problem does it solve?
Managing Tactical RMM from scattered API docs and ad-hoc scripts slows you down when incidents need fast cross-entity answers.
Who is it for?
Self-hosted Tactical RMM users who want MCP-native device and client operations from their IDE agent.
Skip if: Builders without a TRMM instance or teams that only need generic server SSH—not RMM policy APIs.
What do I get? / Deliverables
Your agent can run typed TRMM commands and search mirrored data locally without rebuilding HTTP clients each time.
- Typed MCP tools covering Tactical RMM API endpoints
- Local SQLite datastore for offline and cross-entity queries
- Versioned 0.1.0 MCPB install from GitHub releases
Recommended MCP Servers
Journey fit
How it compares
Tactical RMM API bridge with local mirror, not a cloud RMM product or security audit skill.
Common Questions / FAQ
Who is Tactical RMM MCP for?
It is for MSPs and indie IT admins running Tactical RMM who want MCP tools for endpoints, clients, and scripts from Claude Code or Cursor.
When should I use Tactical RMM MCP?
Use it during monitoring and incident workflows when you need quick API actions and offline SQLite search across TRMM entities.
How do I add Tactical RMM MCP to my agent?
Add the mcpb package with stdio transport and set TRMM_API_KEY in your MCP client environment using the Servosity release artifact.