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

# major org

> Switch between organizations and inspect membership from the CLI.

The `org` commands help you view and select organizations.

| Command            | Purpose                        |
| ------------------ | ------------------------------ |
| `major org list`   | List all your organizations.   |
| `major org select` | Select a default organization. |
| `major org whoami` | Show the current organization. |

## `major org list`

```bash theme={null}
major org list
```

**When to use:** viewing your available organizations.

**What happens:**

Lists all organizations you belong to and highlights the currently selected one.

## `major org select`

```bash theme={null}
major org select
```

**When to use:** switching between organizations.

**What happens:**

1. Lists your available organizations.
2. Allows you to select a new default organization.
3. Updates your local configuration.

## `major org whoami`

```bash theme={null}
major org whoami
```

**When to use:** checking which organization is currently selected.

**What happens:**

Displays the name and ID of the currently selected organization.

## Organization resources via MCP

The CLI exposes organization-level resources through MCP endpoints. You can authenticate using Bearer tokens and access organization resources without requiring an application context.

**Available org-level MCP capabilities:**

* List all resources in your organization.
* Check AI proxy status for resources.
* Get app status across your organization.
* Read resource context documents.
* Interact with resources through MCP tools.
* Select and manage environments for resource operations.

**Authentication:**

Authenticate to org-level MCP endpoints using a Bearer token. Include your token in the request header:

```bash theme={null}
Authorization: Bearer <your-token>
```

The CLI MCP server enforces resource permissions consistently across both app-level and org-level access modes through unified permission checking.

### Environment selection in MCP

The org-scoped MCP provides tools to select which environment resource tools operate in:

* `set_environment` – Switch the active environment for resource operations. The choice persists across sessions.
* `get_environment` – Check which environment is currently active.

By default, resource operations use the default build environment. Use these tools to work with resources in a different environment, such as staging or production. This environment selection is separate from the per-app environment choice available in the web editor.

<Card title="Learn more about Resources" icon="box" href="/cli/resource">
  See how to manage connectors and resources for your applications.
</Card>