Skip to main content
Aeolo has one intended mental model: 
User or agent intent
  -> command name
  -> selected domain
  -> remote command registry or local-only operation
  -> structured result

​
Two execution surfaces

SurfaceBest forExample
CLIHumans, shell agents, local filesaeo content import --body-file draft.md
MCPRemote AI agentsaeo_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: 
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:
CommandWhy
aeo auth loginOpens a browser and writes local credentials.
aeo auth logoutMutates local config.
aeo updateUpdates the local binary.
aeo drive downloadWrites a file to the local filesystem.
aeo image upload --fileReads local files.
MCP clients should use bearer tokens and remote URLs instead of local files where possible.