Kilo IoT Platform

by Kilo IoT

Recommended SSE
699 downloads
Not rated
GitHub Website

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

Author
Kilo IoT
Downloads
699
Transport
SSE
Categories
Cloud Service, Other, Infrastructure

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:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Kilo IoT Platform
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. 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"
    }
  }
}

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.

MCPis an open standard that lets an AI client discover and call tools on a remote server. Because it is a standard rather than a per-vendor integration, any MCP client can connect — Claude Code, Claude Desktop, ChatGPT, Codex, Cursor and others — over Streamable HTTP.

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?

ThePublic REST APIis for programs you write: a sync job, a reporting pipeline, a bridge to another system. It authenticates with a scoped API key that runs unattended. MCP is for an AI client acting on your behalf, authorized by your own sign-in. If you are writing code, use REST. If you are working with an assistant, use MCP.

- 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.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.