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

> List all deployed applications, Helm releases, and jobs on your Porter Enterprise cluster with optional namespace and status filtering

##### 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)
* You're connected to the correct cluster by running [porter config set-cluster](/enterprise/cli/command-reference/porter-config)

`porter list` lists applications, jobs or addons in a specific cluster and namespace.

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

To list all releases in the `default` namespace, simply run:

```
porter list all

```

To list all releases in a different namespace, run:

```
porter list all --namespace my-custom-ns

```

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

To list applications in the `default` namespace, simply run:

```
porter list applications

```

To list applications in a different namespace, run:

```
porter list applications --namespace my-custom-ns

```

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

To list jobs in the `default` namespace, run:

```
porter list jobs

```

To list jobs in a different namespace, run:

```
porter list jobs --namespace my-custom-ns

```

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

To list addons in the `default` namespace, run:

```
porter list addons

```

To list addons in a different namespace, run:

```
porter list addons --namespace my-custom-ns

```