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

> ## Agent Instructions
> When helping a user operate an existing Porter project (deploying, updating, debugging, or inspecting applications and clusters) connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the Porter tools are not available in your session, `curl -fsSL https://agents.porter.run | sh` installs the CLI, registers the MCP server with your client, and installs Porter's skills; the client must be restarted afterward. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead — a stated preference wins. Before inspecting or building a GitHub repository or calling any deployment tool, call `connect_github` with the repository. Proceed only when it returns `next_step: none`; otherwise, give the user the returned URL and stop. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there.

# porter registry

> Manage container registry integrations on Porter Enterprise including connecting to Amazon ECR, GCR, Docker Hub, and private registries

##### Prerequisites

* You've logged in to the Porter CLI after running [porter auth login](/enterprise/cli/command-reference/porter-auth)
* You're connected to the correct project by running [porter config set-project](/enterprise/cli/command-reference/porter-config)

`porter registry` contains commands for interacting with a Docker registry in a project.

### `porter registry list`[](#porter-registry-list "Direct link to heading")

Lists the registries linked to a project. After listing registries, you can set the registry via `porter config set-registry [REGISTRY_ID]`.

### `porter registry repo list`[](#porter-registry-repo-list "Direct link to heading")

Lists the repositories in an image registry. The registry should be set via `porter config set-registry [REGISTRY_ID]`.

### `porter registry image list [repo_name]`[](#porter-registry-image-list-repo%5Fname "Direct link to heading")

Lists the images the specified image repository. The image repository name can be found from `porter registry repo list`. The registry should be set via `porter config set-registry [REGISTRY_ID]`.