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

> Retrieve details about deployed applications on Porter Enterprise including release status, values, and configuration from the CLI

##### 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 get` fetches basic information about a Porter application. It also supports outputting in the JSON and YAML formats.

#### Examples[](#examples "Direct link to heading")

To get information about a release named `sample-app`, you can run the following:

```
porter get sample-app

```

This command is namespace-scoped and uses the default namespace. To specify a different namespace, use the `--namespace` flag:

```
porter get sample-app --namespace custom-namespace

```

To output in a data interchange format such as JSON, use the `--output` flag:

```
porter get sample-app --output json

```

And similarly for YAML:

```
porter get sample-app --output yaml

```

### `porter get values`[](#porter-get-values "Direct link to heading")

This command can be used to fetch the Helm values of a release. For instance, to get the Helm values of a release named `sample-app`, you can run the following:

```
porter get values sample-app

```
