Open AIoT · Docs

Documentation

The specification, guides and governance — everything starts here. The spec is published as versioned nodes; v0.x releases are Drafts open to iteration.

Coming soon

5-Minute QuickstartPinned

1

Install the MCP server

Get the reference implementation from GitHub Releases — self-host with one command.

2

Configure your client

Add one entry to the mcpServers config of your AI client.

3

Connectivity test

Ask the AI to list your devices — your first AI-controls-device moment.

Start the quickstart

Specification

The Open AIoT specification itself: L0 capability model, L1 AI access protocol, L2 authorization & security — published as versioned nodes.

L0 Capability Modelv0.1 How a device describes itself to AI: a standard capability descriptor made of properties, actions and events.
L1 AI Access Protocol (MCP Binding)v0.1 How AI platforms connect: an MCP binding that maps L0 capabilities into AI-callable tools.
L2 Authorization & Security Modelv0.1 Scoped authorization, magic links, human-in-the-loop confirmation and call auditing.

Guides

Start with the 5-minute quickstart, then per-platform setup tutorials for AI clients and collaboration apps.

5-Minute Quickstart Install the MCP server, configure your client, run a connectivity test — first AI-controls-device in minutes.
Kimi SetupWIP Connect the Open AIoT MCP server in Kimi.
Claude Desktop SetupWIP Connect the Open AIoT MCP server in Claude Desktop.
Cursor SetupWIP Connect the Open AIoT MCP server in Cursor.
Feishu ConnectorWIP Use the Feishu connector bot to command devices right in a chat group.
WeCom ConnectorWIP Use the WeCom connector bot to command devices right in a chat group.
DingTalk ConnectorWIP Use the DingTalk connector bot to command devices right in a chat group.
WorkBuddy ConnectorWIP Use the WorkBuddy connector bot to command devices from your workbench.

Governance

Versioning policy, the RFC process and licensing — open, vendor-neutral governance.

Versioning Policy v0.x releases are Drafts open to iteration; stability guarantees start at v1.0.
RFC Index Anyone can propose changes to the spec — how RFCs are raised, discussed and settled.
License The spec and reference implementations are open-source licensed — see each repository's LICENSE file.

About versions & Drafts

The specification is published as versioned nodes (e.g. “L0 Capability Model v0.1”), newest first, with older nodes archived. v0.x nodes are Drafts — open to iteration with no compatibility promises — and their pages automatically carry a Draft banner; stability guarantees start at v1.0.

Changes to the spec go through the RFC process: see the Versioning Policy and the RFC Index, or start a discussion in the Open-AIoT organization on GitHub.