Mender

You will deploy and connect the Mender MCP Server to your Mender IoT platform, enabling AI assistants to interact with devices, deployments, and inventory through secure, read-only operations and natural language commands.

How to use

You will install and configure the Mender MCP Server to connect an MCP client, such as Claude Code, to your hosted or on-premise Mender instance. Once configured, you can query device status, monitor deployments, inspect inventories and artifacts, view logs, and perform read-only checks across your fleet. Use natural language commands to list devices, track deployments, retrieve hardware specifications, explore releases, and inspect audit logs. The server enforces token-based authentication and input validation to keep interactions secure while you monitor and analyze your fleet.

How to install

Prerequisites: you need Python 3.8 or newer, an active hosted Mender account (or access to your on-premise Mender), and an MCP client capable of using MCP.

Step 1: Install from source

# Clone the repository
git clone https://github.com/pasinskim/mender-mcp.git
cd mender-mcp

# Create and activate virtual environment
python3 -m venv venv
source venv/bin/activate  # On Windows: venv\\Scripts\\activate

# Install the package
pip install -e .

Step 2: Verify installation

mcp-server-mender --help

Configuration and usage notes

Configure your Mender MCP Server connection in your MCP client setup. You can connect using a token supplied by Mender, or reference a token file. For hosted Mender, use the hosted URL. For on-premise installations, provide your Mender server URL.

Security, tokens, and best practices

Use token-based authentication and secure storage for tokens. Rotate tokens regularly and grant only the minimal permissions needed for device management and deployment monitoring. Never expose tokens in plain text or commit them to version control.

Troubleshooting

If you encounter authentication errors, verify that your access token is valid and has the necessary permissions. Check the server URL, network connectivity, and token formatting. For configuration problems, ensure the MCP server command and arguments match the examples shown in your setup.

Notes

This MCP server setup supports both hosted Mender deployments and on-premise installations. The provided configurations show how to run the MCP server locally and connect to Mender using either a token in an environment variable or a token file.

Available tools

get_device_status

Retrieve the current status of a specific device, including online status, last seen, and health indicators.

list_devices

List devices with optional filters such as status, device type, and limit to control the result set.

get_deployment_status

Check the progress and details of a specific deployment.

list_deployments

List deployments with optional status filters and limits.

get_deployment_device_log

Fetch deployment logs for a particular device to aid troubleshooting.

get_deployment_logs

Retrieve deployment logs for all devices participating in a deployment.

get_release_status

Get detailed information about a specific release, including artifacts and compatibility.

list_releases

List releases with filtering by name, tag, or limit.

get_device_inventory

Get complete inventory attributes for a specific device.

list_device_inventory

List device inventories with filtering options.

get_inventory_groups

Obtain groups of devices by their inventory attributes.

get_audit_logs

Fetch Mender audit logs with comprehensive filtering by user, action, date range, and object type.