Skip to main content
Glama

Level.io RMM MCP Server

CI

An unofficial Model Context Protocol (MCP) server for Level.io, the modern remote monitoring and management (RMM) platform for IT teams and managed service providers (MSPs). Connect AI clients such as Codex or Claude Desktop to the Level v2 REST API for endpoint inventory, monitoring alerts, automations, groups, tags, custom fields, and available updates.

This community project is not affiliated with or endorsed by Level Software, Inc.

What is Level.io?

Level.io is a remote monitoring and management platform for managing Windows, macOS, and Linux devices across IT environments. Level describes its broader RMM product around unified device management, proactive monitoring and alerting, intelligent automation, centralized patch management, remote control, scripting, and asset inventory.

This MCP server covers the operations currently available in Level's public v2 API. It does not imply API access to every feature in the Level web application.

Related MCP server: addigy-mcp

Level.io MCP tools

The server generates 35 typed MCP tools from Level's published OpenAPI specification:

  • Devices and endpoint inventory: list devices, inspect hardware and operating-system details, update device metadata, move devices between groups, and delete devices

  • Monitoring and alerting: list alerts, inspect alert details, filter active or resolved alerts, and resolve alerts

  • RMM automations: list automations and webhook triggers, inspect automation runs, and trigger configured automation webhooks

  • Groups: list, create, update, and delete groups; assign devices to groups or remove them

  • Tags: list, create, update, and delete tags; apply tags to devices or remove them

  • Custom fields: manage custom-field definitions and values for organizations, groups, and devices

  • Available updates: list and inspect software or operating-system updates reported by Level

Tool schemas preserve Level's required fields, enums, nullable values, pagination cursors, and webhook variables. The API key is server configuration and is never exposed as an MCP tool argument.

Common AI-assisted RMM workflows

  • Find devices or endpoints by hostname, serial number, group, or tag

  • Review device inventory, operating-system, CPU, memory, disk, network, motherboard, and security data

  • Triage active monitoring alerts and resolve handled alerts

  • Organize endpoints with Level groups, tags, and custom fields

  • Inspect available or installed updates by device, status, or category

  • Discover and trigger Level automation webhooks

Mutation tools are annotated so compatible MCP clients can distinguish read-only operations from writes and destructive actions.

Requirements

  • Node.js 20 or newer

  • A Level.io API key created under Settings → API Keys in Level

Use a read-only API key for inventory, reporting, or alert review. Use a read-and-write key only when the MCP client needs to create, update, resolve, trigger, or delete Level resources. See Level's public API guide.

Install locally

git clone https://github.com/pbozzay/level-mcp.git
cd level-mcp
npm ci
npm run build

Configure Codex

Codex reads MCP servers from ~/.codex/config.toml. Use the absolute path to the built dist/index.js file.

The simplest configuration stores the Level.io API key directly in your Codex configuration:

[mcp_servers.level]
command = "node"
args = ["C:\\absolute\\path\\to\\level-mcp\\dist\\index.js"]
startup_timeout_sec = 15
tool_timeout_sec = 60
default_tools_approval_mode = "writes"

[mcp_servers.level.env]
LEVEL_API_KEY = "your-level-api-key"

config.toml is a local user file, but this method stores the key there as plaintext. Never commit that file or the key to Git.

To keep the key out of config.toml, allow Codex to forward it from the environment instead:

[mcp_servers.level]
command = "node"
args = ["C:\\absolute\\path\\to\\level-mcp\\dist\\index.js"]
env_vars = ["LEVEL_API_KEY"]
default_tools_approval_mode = "writes"

Set LEVEL_API_KEY before launching Codex, then fully restart the Codex app, CLI, or IDE extension. Use /mcp or the MCP servers settings page to confirm that level is connected.

Configure another MCP client

For clients that use JSON MCP configuration, use the same built entry point:

{
  "mcpServers": {
    "level": {
      "command": "node",
      "args": ["C:/absolute/path/to/level-mcp/dist/index.js"],
      "env": {
        "LEVEL_API_KEY": "your-level-api-key"
      }
    }
  }
}

Restart the MCP client after changing its configuration. Keep configuration files containing API keys private.

Run directly

Set LEVEL_API_KEY to the value Level expects in its Authorization header, then start the stdio server:

LEVEL_API_KEY="your-level-api-key" npm start

PowerShell:

$env:LEVEL_API_KEY = "your-level-api-key"
npm start

Configuration

Environment variable

Required

Default

Purpose

LEVEL_API_KEY

Yes for authenticated operations

—

Value sent in the Level API Authorization header

LEVEL_API_BASE_URL

No

https://api.level.io

Alternate Level API origin for a proxy or test server

LEVEL_API_TIMEOUT_MS

No

30000

Per-request timeout in milliseconds

Level automation webhooks can be configured without authorization. The server therefore permits triggerWebhook without LEVEL_API_KEY; when a key is configured, it is sent.

Development

npm run check
npm test
npm run build

Refresh the checked-in Level v2 OpenAPI document whenever Level publishes API schema changes:

npm run spec:update

The server communicates over MCP stdio. API failures and argument-validation failures become MCP tool errors; successful JSON responses are returned as readable text and structured content.

License and trademarks

The source code is available under the MIT License. Level, Level.io, and related product names are trademarks of their respective owners. This repository is an independent open-source integration.

Available Tools

35 tools
assignGroupDevicesAssign devices to groupB

Assign devices to group. Assigns the specified devices to the given group. Level API endpoint: POST /v2/groups/{id}/devices

Inputs: id (required), device_ids (required).

createCustomFieldCreate custom fieldC

Create custom field. Creates a custom field. Level API endpoint: POST /v2/custom-fields

Inputs: name (required), admin_only.

createGroupCreate groupC

Create group. Creates a new group. Level API endpoint: POST /v2/groups

Inputs: name (required), parent_id.

createTagCreate tagC

Create tag. Creates a new tag. Level API endpoint: POST /v2/tags

Inputs: name (required).

deleteCustomFieldDelete custom fieldB
DestructiveIdempotent

Delete custom field. Deletes a custom field. Level API endpoint: DELETE /v2/custom-fields/{id}

Inputs: id (required).

deleteCustomFieldValueDelete custom field valueB
DestructiveIdempotent

Delete custom field value. Deletes a custom field value for the organization, group, or device. Level API endpoint: DELETE /v2/custom-field-values

Inputs: custom_field_id (required), force, assigned_to_id.

deleteDeviceDelete deviceB
DestructiveIdempotent

Delete device. Deletes the specified device. Level API endpoint: DELETE /v2/devices/{id}

Inputs: id (required).

deleteGroupDelete groupA
DestructiveIdempotent

Delete group. Deletes an existing group. Level API endpoint: DELETE /v2/groups/{id}

Inputs: id (required).

deleteTagDelete tagC
DestructiveIdempotent

Delete tag. Deletes a tag. Level API endpoint: DELETE /v2/tags/{id}

Inputs: id (required).

listAlertsList alertsB
Read-onlyIdempotent

List alerts. Returns a list of your alerts. Level API endpoint: GET /v2/alerts

Inputs: limit, status, device_id, ending_before, +1 more.

listAutomationsList automationsA
Read-onlyIdempotent

List automations. Returns a list of non-archived automations. Level API endpoint: GET /v2/automations

Inputs: limit, ending_before, starting_after.

listAutomationWebhooksList automation webhooksA
Read-onlyIdempotent

List automation webhooks. Returns webhook trigger URLs and accepted parameters for non-archived automations. Level API endpoint: GET /v2/automations/webhooks

Inputs: limit, ending_before, starting_after.

listCustomFieldsList custom fieldsB
Read-onlyIdempotent

List custom fields. Returns a list of custom fields. Level API endpoint: GET /v2/custom-fields

Inputs: limit, ending_before, starting_after.

listCustomFieldValuesList custom field valuesA
Read-onlyIdempotent

List custom field values. Returns a list of custom field values for the organization, groups, or devices. Level API endpoint: GET /v2/custom-field-values

Inputs: limit, ending_before, assigned_to_id, starting_after, +1 more.

listDevicesList devicesA
Read-onlyIdempotent

List devices. Returns a list of your devices. Level API endpoint: GET /v2/devices

Inputs: limit, tag_id, group_id, hostname, +11 more.

listGroupsList groupsA
Read-onlyIdempotent

List groups. Returns a list of your groups. Level API endpoint: GET /v2/groups

Inputs: limit, parent_id, ending_before, starting_after.

listTagsList tagsC
Read-onlyIdempotent

List tags. Returns a list of tags. Level API endpoint: GET /v2/tags

Inputs: limit, device_id, ending_before, starting_after.

listUpdatesList updatesB
Read-onlyIdempotent

List updates. Returns a list of your updates. Level API endpoint: GET /v2/updates

Inputs: limit, status, category, device_id, +2 more.

removeGroupDevicesRemove devices from groupA
DestructiveIdempotent

Remove devices from group. Removes the specified devices from the group. Level API endpoint: DELETE /v2/groups/{id}/devices

Inputs: id (required), device_ids (required).

removeTagFromDevicesRemove tag from devicesB
DestructiveIdempotent

Remove tag from devices. Removes a tag from the provided devices. Level API endpoint: DELETE /v2/tags/{id}/devices

Inputs: id (required), device_ids (required).

resolveAlertResolve alertA

Resolve alert. Resolves an active alert. If the alert is already resolved, this is a no-op and returns the alert as-is. Level API endpoint: POST /v2/alerts/{id}/resolve

Inputs: id (required).

showAlertShow alertA
Read-onlyIdempotent

Show alert. Retrieves the details of an existing alert. Level API endpoint: GET /v2/alerts/{id}

Inputs: id (required).

showAutomationRunShow automation runB
Read-onlyIdempotent

Show automation run. Retrieves the status of an existing automation run. Level API endpoint: GET /v2/automation-runs/{id}

Inputs: id (required), include_steps.

showCustomFieldShow custom fieldA
Read-onlyIdempotent

Show custom field. Retrieves the details of an existing custom field. Level API endpoint: GET /v2/custom-fields/{id}

Inputs: id (required).

showDeviceShow deviceA
Read-onlyIdempotent

Show device. Retrieves the details of an existing device. Level API endpoint: GET /v2/devices/{id}

Inputs: id (required), include_cpus, include_disks, include_memory, +4 more.

showGroupShow groupA
Read-onlyIdempotent

Show group. Retrieves the details of an existing group. Level API endpoint: GET /v2/groups/{id}

Inputs: id (required).

showTagShow tagA
Read-onlyIdempotent

Show tag. Retrieves a tag. Level API endpoint: GET /v2/tags/{id}

Inputs: id (required).

showUpdateShow updateA
Read-onlyIdempotent

Show update. Retrieves the details of an existing update. Level API endpoint: GET /v2/updates/{id}

Inputs: id (required).

tagDevicesTag devicesC

Tag devices. Applies a tag to the provided devices. Level API endpoint: POST /v2/tags/{id}/devices

Inputs: id (required), device_ids (required).

triggerWebhookTrigger webhookA

Trigger webhook. Triggers an automation via a webhook. Webhooks that require an authorization header must include a write-enabled API key. Level API endpoint: POST /v2/automations/webhooks/{token}

Inputs: token (required), device_ids.

updateCustomFieldUpdate custom fieldC
Idempotent

Update custom field. Updates a custom field. Level API endpoint: PATCH /v2/custom-fields/{id}

Inputs: id (required), name, admin_only.

updateCustomFieldValueUpdate custom field valueA
Idempotent

Update custom field value. Set a custom field value for the organization, group, or device. Level API endpoint: PATCH /v2/custom-field-values

Inputs: value (required), custom_field_id (required), force, assigned_to_id.

updateDeviceUpdate deviceC
Idempotent

Update device. Updates the specified device. Level API endpoint: PATCH /v2/devices/{id}

Inputs: id (required), name, notes, group_id.

updateGroupUpdate groupC
Idempotent

Update group. Updates an existing group. Level API endpoint: PATCH /v2/groups/{id}

Inputs: id (required), name, parent_id.

updateTagUpdate tagB
Idempotent

Update tag. Updates an existing tag. Level API endpoint: PATCH /v2/tags/{id}

Inputs: id (required), name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., listDevices vs. showDevice vs. updateDevice). No two tools appear to perform the same operation, and even similar actions like tagDevices and removeTagFromDevices are clearly separated. The tool set is well-organized by resource.

    Naming Consistency5/5

    Tool names follow a consistent verb-noun pattern in camelCase (list, show, create, update, delete, assign, remove, tag, trigger, resolve). Multi-word actions like assignGroupDevices and removeTagFromDevices remain readable and consistent with the pattern.

    Tool Count2/5

    With 35 tools, the server is above the 25-tool threshold for 'too many'. While the broad scope covers multiple resource types (devices, groups, tags, custom fields, alerts, updates, automations), the sheer number creates a heavy surface that may overwhelm agents. A more focused set would improve usability.

    Completeness2/5

    The surface has significant gaps: there is no createDevice, and custom field values lack an explicit create operation. Alerts only support list/show/resolve, updates only support list/show, and automations are missing create/update/delete. These omissions will force agents to work around missing core operations, especially for device lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.
      21
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Unified MCP server for Addigy device management, exposing both v2 and legacy v1 APIs to query devices, alerts, policies, and applications.
      -