> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heyniblet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Niblet MCP overview

> Manage displays and developer records from an OAuth-capable AI client.

Niblet provides one remote Streamable HTTP MCP endpoint:

```text theme={null}
https://cloud.heyniblet.com/mcp
```

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.

<CardGroup cols={2}>
  <Card title="Connect a client" icon="plug" href="/mcp/connect" />

  <Card title="Control displays" icon="display" href="/mcp/display-control" />

  <Card title="Manage developer apps" icon="code-branch" href="/mcp/developer-apps" />

  <Card title="Review the security model" icon="shield-check" href="/mcp/security" />
</CardGroup>