{
  "markdown": "# Kilo IoT Platform MCP Server\n\n[![smithery badge](https://smithery.ai/badge/kiloiot/kilo-iot-platform)](https://smithery.ai/servers/kiloiot/kilo-iot-platform)\n\nConnect an AI client to a live IoT deployment and let it work the real thing: read devices, provision\nhardware, deploy automation rules, work the alarm queue, and send commands to physical equipment.\n\nThe server is hosted by [Kilo IoT](https://kiloiot.io) — there is nothing to install and no API key to\nmint. You sign in with your usual Kilo account in the browser, and the connection carries your own\npermissions.\n\n```\nhttps://mcp-auth.kiloiot.io/mcp\n```\n\nThis repository holds the public metadata for that server: its registry manifest, its icon, and the\nsetup instructions below. The service itself is closed-source.\n\n## What is the Model Context Protocol?\n\n[MCP](https://modelcontextprotocol.io) is an open standard that lets an AI client discover and call\ntools on a remote server. Because it is a standard rather than a per-vendor integration, any MCP\nclient can connect — Claude Code, Claude Desktop, ChatGPT, Codex, Cursor and others — over Streamable\nHTTP.\n\n## What can an AI agent do with the Kilo MCP server?\n\n| Area | What the connected client can do |\n|---|---|\n| **Devices** | List and inspect devices, read telemetry and diagnostics, provision LoRaWAN devices, MQTT devices and GPS trackers, manage device profiles |\n| **Commands** | List the commands a device supports, send one, and check how it completed — this is where the assistant acts on physical equipment |\n| **Connectors** | Review connectors, create connections for a device to report through |\n| **Rules** | Review rules, generate and deploy automation, simulate logic against real sensor values before it reaches production, stop a running rule, read execution history |\n| **Alarms** | List and resolve alarms, summarize activity for a shift or a site, manage alarm rules and notification channels, send a test notification |\n| **Dashboards** | List dashboards and query the data behind any widget |\n| **Sensors** | Inspect and change sensor mappings, manage sensor templates |\n| **Organization** | Read organization details, list teams, invite users, assign roles |\n\nEvery tool is annotated, so a client knows which ones only read and which ones change something.\nRead-only tools run without interrupting you; anything destructive asks first.\n\n## How do I connect Claude Code to Kilo?\n\n```bash\nclaude mcp add --transport http kilo https://mcp-auth.kiloiot.io/mcp\n```\n\nThen run `/mcp` inside Claude Code, pick `kilo`, and authorize in the browser window that opens. Run\n`/mcp` again to confirm it reports **connected**.\n\n## How do I connect Claude Desktop, ChatGPT, Cursor or Codex?\n\nClients with a connector dialog — Claude Desktop, ChatGPT, Cursor — take the URL directly: open\n**Settings → Connectors** (or Integrations / MCP servers), choose **Add custom connector**, paste\n`https://mcp-auth.kiloiot.io/mcp`, and authorize in the browser.\n\nClients configured from a file or a terminal, such as Codex, register the same URL as a **Streamable\nHTTP** server. Your client's own documentation says where its MCP settings live; nothing about this\nendpoint is client-specific.\n\n## Which organization does the connection see?\n\nBy default, whichever organization is currently selected in the Kilo web app. Switch organizations\nthere and reconnect the client to follow it.\n\nTo pin a client to one organization regardless of what is selected in the web app:\n\n```\nhttps://mcp-auth.kiloiot.io/o/{organizationId}/mcp\n```\n\nThe organization ID comes from the web app. Pinning is worth doing for a workstation that must always\noperate against one production organization — and it cannot be moved by a stray click in the\norganization switcher. Requests for an organization you are not a member of are refused.\n\n## Is it safe to give an AI agent access to my IoT devices?\n\n- **You sign in, not a service account.** Authorization happens in your browser against your normal\n  Kilo account. No key is generated, copied or stored for the connection.\n- **Your permissions are the ceiling.** The client can only do what your account can do. If you cannot\n  deploy a rule or invite a user, neither can it.\n- **Organization boundaries hold**, on the default endpoint and the pinned one alike.\n- **Actions keep their normal records.** Rule changes and executions appear in rule history, device\n  commands in command execution history, and access changes in the Audit Trail.\n\nTreat an authorized client like a signed-in session: it belongs on machines you control.\n\n## MCP server vs REST API — which should I use?\n\nThe [Public REST API](https://docs.kiloiot.io/kilo-iot-server/api/) is for programs you write: a sync\njob, a reporting pipeline, a bridge to another system. It authenticates with a scoped API key that\nruns unattended. MCP is for an AI client acting on your behalf, authorized by your own sign-in. If you\nare writing code, use REST. If you are working with an assistant, use MCP.\n\n## Links\n\n- Platform: [kiloiot.io](https://kiloiot.io) · [Kilo IoT Platform](https://kiloiot.io/iot-server/)\n- Documentation: [docs.kiloiot.io — MCP Server](https://docs.kiloiot.io/kilo-iot-server/api/mcp-server)\n- Support: [kiloiot.io/contact](https://kiloiot.io/contact/)\n- Privacy policy: [kiloiot.io/privacy-policy](https://kiloiot.io/privacy-policy/) · Terms: [kiloiot.io/terms-of-service](https://kiloiot.io/terms-of-service/)\n\nStart free at [kiloiot.io](https://kiloiot.io).\n",
  "bytes": 5494,
  "sha": "adfe53608d54ad7f9c1878bb8440663f61a92e141748fecf812a3419fb694cad",
  "repo_slug": "kiloiot/kilo-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_kiloiot_kilo_a11c6712/readme"
}