Kilo IoT Platform
io.kiloiot由 kiloiot.io 發布官方發布者v1.0.1更新於 Oct 25, 2026
The IoT platform where AI controls real-world devices: read, provision, automate and command.
概覽
Kilo 物聯網平台的託管 MCP 伺服器,讓助理讀取裝置、部署自動化規則、處理告警並向實體裝置送出指令
- 可以做什麼
- 列出並檢視裝置,讀取遙測與診斷資料,開通 LoRaWAN、MQTT 與 GPS 裝置,管理裝置設定檔以及感測器對應與範本。列出裝置支援的指令、送出指令並查看執行結果。檢視連接器並為裝置建立回報連線。檢視並部署自動化規則,用真實感測器數值模擬邏輯,停止執行中的規則,讀取執行歷史。列出並處理告警,彙整活動情況,管理告警規則與通知管道,送出測試通知。列出儀表板並查詢元件背後的資料,讀取組織資訊、列出團隊、邀請使用者並指派角色。
- 適用情境
- 適合在助理需要對實際運作的 Kilo 物聯網部署採取行動、而不只是討論時加入:檢視裝置與遙測、測試與部署規則、清除告警,或向設備下達指令。適合已在用 Kilo、希望助理以本人帳號權限執行操作的使用者。
- 執行需求
- 由 Kilo 託管的遠端 Streamable HTTP 端點,無需安裝,也不需要 API 金鑰。透過瀏覽器 OAuth 以一般 Kilo 帳號登入,連線會沿用該帳號的權限。預設使用 Kilo 網頁應用程式中目前選取的組織,也可改用依組織固定的專用網址。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Kilo IoT Platform,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.kiloiot%2Fkilo/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"kilo-iot-platform": {
"type": "http",
"url": "https://mcp-auth.kiloiot.io/mcp"
}
}
}README
Kilo IoT Platform MCP Server
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.
The server is hosted by Kilo IoT — there is nothing to install and no API key to mint. You sign in with your usual Kilo account in the browser, and the connection carries your own permissions.
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 is the Model Context Protocol?
MCP is 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.
How do I connect Claude Code to Kilo?
Then run /mcp inside Claude Code, pick kilo, and authorize in the browser window that opens. Run
/mcp again to confirm it reports connected.
How do I connect Claude Desktop, ChatGPT, Cursor or Codex?
Clients with a connector dialog — Claude Desktop, ChatGPT, Cursor — take the URL directly: open
Settings → Connectors (or Integrations / MCP servers), choose Add custom connector, paste
https://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 a Streamable HTTP server. 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:
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?
- You sign in, not a service account. Authorization happens in your browser against your normal Kilo account. No key is generated, copied or stored for the connection.
- Your permissions are the ceiling. The client can only do what your account can do. If you cannot deploy a rule or invite a user, neither can it.
- Organization boundaries hold, on the default endpoint and the pinned one alike.
- Actions keep their normal records. Rule changes and executions appear in rule history, device commands in command execution history, and access changes in the Audit Trail.
Treat an authorized client like a signed-in session: it belongs on machines you control.
MCP server vs REST API — which should I use?
The Public REST API is 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.
Links
- 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
Start free at kiloiot.io.
來源:README.md,提交 88c62f0
工具
0版本歷史
1- v1.0.1最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分