> ## Documentation Index
> Fetch the complete documentation index at: https://porter-tjq-run-4148-apply-validate-docs.mintlify.site/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. 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 target

> List and manage deployment targets to control which cluster, namespace, and environment your Porter applications deploy to using the CLI

`porter target` contains commands for managing deployment targets.

## Prerequisites

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

***

## `porter target list`

List all deployment targets in the current cluster.

**Usage:**

```bash theme={null}
porter target list [flags]
```

**Options:**

| Flag        | Description                         |
| ----------- | ----------------------------------- |
| `--preview` | Include preview environment targets |

<CodeGroup>
  ```bash List Targets theme={null}
  porter target list
  ```

  ```bash Include Previews theme={null}
  porter target list --preview
  ```
</CodeGroup>

<Info>
  Deployment targets allow you to deploy the same application to different environments (production, staging, preview) within the same cluster.
</Info>

***

## Using Targets with Deployments

Specify a target when deploying with `porter apply`:

```bash theme={null}
porter apply -f porter.yaml --target staging
```

<Tip>
  Preview environment targets are automatically created when you set up preview environments. See [Preview Environments](/preview-environments/overview) for more details.
</Tip>

***

## Related Commands

* [porter apply](/standard/cli/command-reference/porter-apply) - Deploy to a specific target
* [porter app list](/standard/cli/command-reference/porter-app) - List apps in the current target