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

# Command model

> How CLI and MCP map to the same command registry.

Aeolo has one intended mental model:

```txt theme={null}
User or agent intent
  -> command name
  -> selected domain
  -> remote command registry or local-only operation
  -> structured result
```

## Two execution surfaces

| Surface | Best for                          | Example                                               |
| ------- | --------------------------------- | ----------------------------------------------------- |
| CLI     | Humans, shell agents, local files | `aeo content import --body-file draft.md`             |
| MCP     | Remote AI agents                  | `aeo_execute_command` with `command: "agent context"` |

The CLI and MCP both route most remote commands through the same command registry. Local-only commands remain CLI-only because they depend on local files, browsers, or OS behavior.

## Canonical command shape

Prefer noun-first commands:

```bash theme={null}
aeo agent context
aeo content import
aeo reference style
aeo visibility check run
```

## Local-only commands

Some commands should not be expected to work through MCP:

| Command                   | Why                                           |
| ------------------------- | --------------------------------------------- |
| `aeo auth login`          | Opens a browser and writes local credentials. |
| `aeo auth logout`         | Mutates local config.                         |
| `aeo update`              | Updates the local binary.                     |
| `aeo drive download`      | Writes a file to the local filesystem.        |
| `aeo image upload --file` | Reads local files.                            |

MCP clients should use bearer tokens and remote URLs instead of local files where possible.