Skip to main content
Niblet is an app-driven 64×32 ambient display. Use these guides to bring a display online, create local Starlark apps, connect the remote MCP server, and submit immutable releases for review.

Set up a display

Install firmware, connect Wi-Fi locally, and finish the first pixel test.

Build your first app

Install the CLI, create an app, preview it, and upload a review artifact.

Connect Niblet MCP

Manage displays and developer app records from Codex, ChatGPT, Claude, Cursor, or another MCP client.

Runtime reference

Find the widgets, modules, schemas, limits, and compatibility notes used by Niblet apps.

​
Local-first by design

App source, validation, live preview, and rendering stay on your computer. The developer platform receives source only when you explicitly run niblet apps push, and stores that source with the exact locally rendered WebP as one immutable review artifact. The remote MCP server manages display state and developer records. It does not receive Wi-Fi passwords, app credentials, source edits, or local render jobs.
Niblet preserves useful Pixlet compatibility. Existing Starlark apps can often move with small metadata or service-integration changes, but compatibility does not waive API terms, asset rights, or physical-device testing.