Open AIoT · Developers

Developers come first here.

Open specification, self-hosted MCP server, platform connectors and a skill library — connect your devices and let any AI control them.

Who is a developer

Developer=Workbench=Tenant

On Open AIoT, a developer identity is a workbench — your devices, credentials and call audits all belong to it. One ThingBoot account works across Open AIoT and the ThingBoot platform: register once, use everywhere.

Every developer workbench will get a public homepage at /{token}/ Phase 2

Join & Sign in

No account yet? Register a ThingBoot account to get started.

Register
1

Register

Register a ThingBoot account — one account for the whole platform.

2

Create / enter a workbench

Create your own workbench, or join an existing one.

3

Become a developer

Enable the developer identity in your workbench and start connecting devices.

The full onboarding flow opens in Phase 2 — for now you can register an account and create a workbench.

Resources & Downloads

Fully open source, hosted under the Open-AIoT organization on GitHub.

spec

The Open AIoT specification itself: L0 capability model, L1 AI access protocol, L2 authorization & security.

★ Star Issue

mcp

The MCP server reference implementation: one line of config connects your AI client to Open AIoT devices.

★ Star Issue

connectors

Platform connectors: integration bots for Feishu, WeCom, DingTalk, WorkBuddy and more.

★ Star Issue

skills

The skill library: official, ready-to-use skills for device types and scenarios.

★ Star Issue

sdksPlanned

SDKs in multiple languages to help device makers and developers integrate faster.

Releases & Deployment

Releases of every repository are published on GitHub — grab and go.

MCP Server Releases → Self-host the MCP server →

Start building today.

Read the spec, run the demo — or open an issue on GitHub.

GitHub Try the demo