Skip to main content
MCP manages the hosted record around an app. The local Niblet CLI remains the only developer path for authoring, validating, rendering, and uploading a revision.

​
Available tools

1

Plan the app

Use the assistant to refine the name, stable app ID, summary, description, data sources, and configuration needs.
2

Build locally

Create and edit source on your system. Run niblet apps validate and niblet apps preview until the result is ready.
3

Push with the CLI

Run niblet apps push .. The CLI creates the project when needed and uploads an immutable source-and-WebP pair.
4

Inspect and submit with MCP

Call app_get to confirm the revision, then use app_submit_for_review with its revision UUID.
Submitting through MCP has the same effect as niblet apps submit. It does not grant direct publication access.