Skip to main content
Niblet provides one remote Streamable HTTP MCP endpoint:
Connect it to an MCP client that supports remote HTTP servers and browser OAuth. The client discovers Niblet’s protected-resource metadata and asks you to review read and control permissions before tools become available.

​
What MCP can manage

  • displays, names, brightness, night schedules, and display policies;
  • catalog search and installed app configuration;
  • app order, dwell time, refresh choices, and playback windows;
  • scheduled or manually activated scenes;
  • firmware preferences, updates, and explicit reflashes; and
  • developer project records, metadata, revisions, and review submission.

​
What stays outside MCP

  • Wi-Fi credentials and physical device setup;
  • app credentials and provider tokens;
  • Starlark source editing;
  • local validation, preview, and rendering;
  • revision upload; and
  • direct publication.
Use the Niblet CLI or a local app-building skill for source work. Use MCP for account-scoped management after the local artifact exists.

Connect a client

Control displays

Manage developer apps

Review the security model