Level MCP
Expose every Level RMM endpoint to your agent plus offline SQLite fleet rollups for device and alert questions.
Overview
Level MCP is a MCP server for the Operate phase that surfaces Level RMM endpoints and offline SQLite fleet rollups to coding agents over stdio.
What is this MCP server?
- Wraps Level RMM API endpoints for MCP tool calls
- Local SQLite fleet store for offline cross-entity rollups
- Single secret LEVEL_API_TOKEN required at startup
- stdio mcpb release v0.1.0 from Servosity
- Fills gaps where live Level UI cannot cheaply aggregate across entities
- Server version 0.1.0
- One required secret: LEVEL_API_TOKEN
- stdio MCP transport
Community signal: 1 GitHub stars.
What problem does it solve?
Jumping between Level’s UI and your agent for fleet questions hides patterns across devices, alerts, and clients.
Who is it for?
Micro-MSPs and technical solos on Level RMM who want conversational fleet and alert intelligence.
Skip if: Teams without Level RMM or builders who only need generic uptime checks unrelated to Level’s API.
What do I get? / Deliverables
After you set LEVEL_API_TOKEN and register the server, agents can query RMM data and local rollups for faster monitoring decisions.
- MCP tools backed by Level RMM API endpoints
- Offline SQLite cross-entity fleet rollups
- v0.1.0 packaged stdio server (mcpb)
Recommended MCP Servers
Journey fit
How it compares
Level RMM–native MCP monitor, not a standalone RMM console or infrastructure-as-code skill.
Common Questions / FAQ
Who is Level MCP for?
It is for Level RMM customers who want Claude Code, Cursor, or Codex to call RMM APIs and read offline SQLite fleet summaries.
When should I use Level MCP?
Use it during Operate monitoring when you triage alerts, audit device inventory, or need cross-entity rollups while coding or documenting incidents.
How do I add Level MCP to my agent?
Download the levelio mcpb bundle, export LEVEL_API_TOKEN, and configure the stdio MCP server in your agent’s MCP settings.