Kilo IoT Platform
About
Your AI can finally reach the physical world. Kilo is an AI-first IoT platform for commercial and industrial operations, and this connector hands a live deployment to the AI client you already use. Not an export. Not a
Details
- Transport
- SSE
Explore
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Kilo IoT PlatformCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
{
"mcpServers": {
"kilo-iot-platform": {
"type": "http",
"url": "https://mcp-auth.kiloiot.io/mcp"
}
}
}
alarm_definition_create
Create a new alarm definition for the organisation.
alarm_definition_delete
Permanently delete an alarm definition by its ID. This action is irreversible. Always confirm with the user before calling this tool.
alarm_definition_list
List alarm definitions (rules) for the organisation.
alarm_definition_update
Update an existing alarm definition. Only provided fields are changed.
alarm_get
Get a single alarm event by its ID.
alarm_history
List alarm events within a time range (RFC3339 timestamps).
alarm_list
List alarm events for the organisation with optional filters (status, severity).
alarm_resolve
Resolve an active alarm event, optionally providing a resolution reason.
alarm_stats
Get aggregated alarm statistics: total active/resolved counts and breakdown by severity.
connection_create
Create a new device connection. A connection binds a connector type (e.g. lorawan) to a configuration (e.g. network settings). Required before provisioning physical devices.
connection_delete
Delete a device connection by ID. The connection must belong to the user's organization.
connection_list
List device connections for the organization, optionally filtered by connector type
connector_configure
Configure a connector connection (placeholder - not yet implemented)
connector_list
List all available connector types (lorawan, mqtt_cloud, mqtt_external, etc.)
dashboard_create
Create a new dashboard or folder. Folders can contain dashboards.
dashboard_list
List all dashboards and folders in the organisation as a tree structure.
dashboard_update
Update an existing dashboard or folder. Only provided fields are changed.
device_delete
Permanently delete a digital device by ID or name, along with its sensors, sensor mappings and physical-device binding. Irreversible — require explicit user confirmation before calling. Provide either device_id (UUID) or device_name.
device_diagnostics
Get composite diagnostics for a device by ID or name: metadata + last-seen timestamps for all sensors. Provide either device_id (UUID) or device_name (human-readable name from device.list results).
device_get
Get a single device by ID or name. Provide either device_id (UUID) or device_name (human-readable name from device.list results).
device_list
List all digital devices (end-devices / sensors) in the organization. Each device includes its connectionType (lorawan / mqtt / mqtt_cloud / mqtt_external / tracker, empty if unbound). Use connection_type to return only devices of one type, e.g. all LoRaWAN devices. Gateways / LNS gateways / miners are NOT digital devices and are never returned here — the assistant currently has no tool to list or manage gateways (they are managed in the platform web app); never present a device or connection…
device_profile_create
Create a custom device profile (placeholder - not yet implemented)
device_profile_list
Look up a LoRaWAN device profile template by brand, model and frequency band
device_provision_lorawan
Create a LoRaWAN device, optionally attaching sensors and sensor mappings.
device_provision_mqtt
Create a device that receives INCOMING telemetry over an MQTT-family connection (mqtt_cloud or mqtt_external). This tool only configures the platform to read messages PUBLISHED BY the device — it does NOT publish messages TO the device. The platform does not provide outbound MQTT publish / downlink / actuator-command capability through any tool. If the user asks to control / turn on / turn off / send a command to an MQTT device, refuse per PROTOCOL rule 9, do NOT call this tool as a substitut…
device_provision_tracker
Create a GPS tracker device.
device_telemetry
Get aggregated OHLC telemetry history for device sensors over a time range
device_update
Update an existing device by ID or name. Provide either device_id (UUID) or device_name (human-readable name from device.list results). Set detach_physical_device=true to unbind the physical device (DevEUI / connection / configuration) while keeping the digital device and its sensors.
hardware_search
Search for IoT sensor and gateway hardware in the Kilo Electronics catalog. Returns two independently-labelled buckets: `kilo_catalog` (Kilo Electronics catalog, German-language taxonomy) and `web_search` (web fallback). Each bucket carries its own `status` (`ok` / `empty` / `unavailable` / `skipped`) and its own `results` array — they NEVER overlap. PREFERRED CALL SHAPE: pass `categories` (array of German slugs from the catalog) and optionally `intersect=true` to find products tagged with A…
log_export
Export audit log entries as CSV or JSON. (Not yet available — pending audit-service integration)
log_query
Query audit log entries for the organisation within an optional time range. (Not yet available — pending audit-service integration)
my_permissions
Return the SIGNED-IN user's own role (owner/admin/operator/viewer/billing, or custom for a non-standard permission set), ownership status, and granted permissions in the current organisation. ALWAYS call this to answer any question about the current user's OWN role, permissions, or whether they are the owner (e.g. "what are my rights?", "am I the owner?"). Never claim the user is the owner or has any specific role without calling this tool; never infer the current user's role from team_list, …
notification_channel_configure
Enable or disable a user's notification channel (email, SMS, push).
notification_recipient_list
List notification channels (email, SMS, push) for a user.
notification_test
Send a test notification to verify channel delivery. (Feature not yet implemented)
org_get
Get organisation details: name, owner, creation date.
org_update
Update the organisation name or transfer ownership to another user.
recommend_products
Declare your final product recommendation to the user. Call AFTER one or more hardware_search calls have populated your context with candidates. This tool is your ONLY visible output for a recommendation turn — the UI renders the `summary` text above the resolved product cards as a single block. Do not emit any free-form prose around this call; everything the user should read goes into `summary`. Use this to compose a curated answer: pick a single product for a single need, or a package of se…
rule_delete
Move a rule definition to trash (soft delete). The rule can be restored from trash.
rule_example_get
Get a worked Chirp BPMN rule example for an approved AITaxonomy use case ID. Returns the canonical alarm_definition shape (severity, escalation), rule flow steps (CEL expressions), sensor template hints, and design notes. Call BEFORE `rule_provision` when the user's request matches one of the shipped IDs. Currently shipped (curated, not generative): AG-DIST-SILO-001, AG-DIST-TANK-001, AG-DIST-TROUGH-001, PM-DIST-WATER-001, PM-DIST-WATER-003.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"kilo iot platform": {
"kilo-iot-platform": {
"type": "http",
"url": "https://mcp-auth.kiloiot.io/mcp"
}
}
}
}McpServers
{
"kilo-iot-platform": {
"type": "http",
"url": "https://mcp-auth.kiloiot.io/mcp"
}
}The IoT platform where AI controls real-world devices — ask what's happening on site, then tell it to act.
Connect an AI client to a live IoT deployment and let it work the real thing: read devices, provision hardware, deploy automation rules, work the alarm queue, and send commands to physical equipment.
This repository holds the public metadata for that server: its registry manifest, its icon, and the setup instructions below. The service itself is closed-source.
What can an AI agent do with the Kilo MCP server?
Every tool is annotated, so a client knows which ones only read and which ones change something. Read-only tools run without interrupting you; anything destructive asks first.
claude mcp add --transport http kilo https://mcp-auth.kiloiot.io/mcp
Then run/mcpinside Claude Code, pickkilo, and authorize in the browser window that opens. Run/mcpagain to confirm it reportsconnected.
How do I connect Claude Desktop, ChatGPT, Cursor or Codex?
Clients with a connector dialog — Claude Desktop, ChatGPT, Cursor — take the URL directly: openSettings → Connectors(or Integrations / MCP servers), chooseAdd custom connector, pastehttps://mcp-auth.kiloiot.io/mcp, and authorize in the browser.
Clients configured from a file or a terminal, such as Codex, register the same URL as aStreamable HTTPserver. Your client's own documentation says where its MCP settings live; nothing about this endpoint is client-specific.
Which organization does the connection see?
By default, whichever organization is currently selected in the Kilo web app. Switch organizations there and reconnect the client to follow it.
To pin a client to one organization regardless of what is selected in the web app:
https://mcp-auth.kiloiot.io/o/{organizationId}/mcp
The organization ID comes from the web app. Pinning is worth doing for a workstation that must always operate against one production organization — and it cannot be moved by a stray click in the organization switcher. Requests for an organization you are not a member of are refused.
Is it safe to give an AI agent access to my IoT devices?
Treat an authorized client like a signed-in session: it belongs on machines you control.
MCP server vs REST API — which should I use?
- Platform:kiloiot.io·Kilo IoT Platform
- Documentation:docs.kiloiot.io — MCP Server
- Support:kiloiot.io/contact
- Privacy policy:kiloiot.io/privacy-policy· Terms:kiloiot.io/terms-of-service
MCP server for Azure IoT Hub - device registry, twins, direct methods, jobs, messaging
Home automation you can just talk to. No dashboards, no app to learn.
An MCP server for interacting with the ThingsPanel IoT platform.
Access the Cumulocity IoT platform to manage devices, measurements, and alarms.
Digi Remote Manager MCP allows users to connect Ai Agents to their Digi Remote Manager account for analyzing fleet data and help with troubleshooting.
Interact with the Flespi telematics platform API for fleet management, device tracking, and telemetry data processing.
A read-only API for querying and retrieving contextual information about devices and fleets using the Flight Control MCP server.
Enables LLMs and intelligent systems to interact with Litmus Edge for device configuration, monitoring, and management.
Integrates with the Slide API for device and infrastructure management.
Integrate and control SmartThings devices using a personal access token.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
