> ## 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.

# Manage developer apps with MCP

> Create project records, update metadata, inspect revisions, and submit a CLI-uploaded release.

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

| Tool                    | Purpose                                         |
| ----------------------- | ----------------------------------------------- |
| `app_list`              | List hosted developer projects                  |
| `app_get`               | Read one project and immutable revision history |
| `app_create`            | Create an app record before the first CLI push  |
| `app_update`            | Change public name, summary, and description    |
| `app_submit_for_review` | Submit one existing immutable revision          |

## Recommended flow

<Steps>
  <Step title="Plan the app">
    Use the assistant to refine the name, stable app ID, summary, description, data sources, and configuration needs.
  </Step>

  <Step title="Build locally">
    Create and edit source on your system. Run `niblet apps validate` and `niblet apps preview` until the result is ready.
  </Step>

  <Step title="Push with the CLI">
    Run `niblet apps push .`. The CLI creates the project when needed and uploads an immutable source-and-WebP pair.
  </Step>

  <Step title="Inspect and submit with MCP">
    Call `app_get` to confirm the revision, then use `app_submit_for_review` with its revision UUID.
  </Step>
</Steps>

Submitting through MCP has the same effect as `niblet apps submit`. It does not grant direct publication access.