Kilo IoT Server

What Kilo IoT Server MCP server does

Kilo IoT Server MCP server gives an AI client access to a live Kilo IoT deployment. It covers both operational data and actions against connected equipment. An authorized client can inspect devices, telemetry, diagnostics, profiles, connectors, rules, alarms, dashboards, sensor mappings, teams, and organization details.

The server also supports actions that change a deployment. These include provisioning LoRaWAN devices, MQTT devices, and GPS trackers; creating device connections; deploying or stopping automation rules; resolving alarms; sending test notifications; inviting users; assigning roles; and sending commands to physical devices. Rule simulations can run against real sensor values before deployment.

How it works

The hosted endpoint uses the Model Context Protocol over Streamable HTTP:

https://mcp-auth.kiloiot.io/mcp

The repository contains public metadata, an icon, and setup information; the hosted service itself is closed-source. Authentication takes place in a browser through the user's normal Kilo account. No local installation or separately generated API key is required, and the connection inherits the account's Kilo permissions.

The default endpoint operates on the organization currently selected in the Kilo web application. A client can instead use an organization-specific endpoint containing an organization ID. Requests for an organization where the user is not a member are rejected. Tool annotations identify read-only and changing operations, allowing clients to treat them differently; destructive actions require confirmation.

Setup and configuration

For Claude Code, register the Streamable HTTP endpoint with:

claude mcp add --transport http kilo https://mcp-auth.kiloiot.io/mcp

Run /mcp in Claude Code, select kilo, authorize in the browser, and check the connection status with /mcp again.

Claude Desktop, ChatGPT, and Cursor can add the same URL through their connector or integration settings and then complete browser authorization. Clients configured through a file or terminal, including Codex, should register it as a Streamable HTTP server. To pin access to one organization, use https://mcp-auth.kiloiot.io/o/{organizationId}/mcp.

Tools and capabilities

Available capability areas include:

• Listing and inspecting devices, telemetry, diagnostics, profiles, and supported commands.
• Provisioning LoRaWAN, MQTT, and GPS-tracking hardware.
• Sending device commands and checking their execution results.
• Reviewing, generating, simulating, deploying, stopping, and auditing automation rules.
• Listing and resolving alarms, managing alarm rules and notification channels, and sending test notifications.
• Listing dashboards and querying the data used by widgets.
• Managing sensor mappings and templates, connectors, teams, invitations, and roles.

Limitations and notes

Kilo IoT Server MCP server is intended for an AI client acting through a user's sign-in, not for unattended application code. Programs such as synchronization jobs, reporting pipelines, or system bridges should use Kilo's REST API with a scoped API key instead.

The client cannot exceed the signed-in account's permissions or cross organization boundaries. Actions remain visible in Kilo records, including rule history, command execution history, and the Audit Trail. Because the connection can operate physical equipment and alter production configuration, authorize it only on machines you control and review changing actions before approval.