# CLI and MCP reference

Use Vision from a terminal or an agent with the exact installed commands, tools, and result shapes.

Use the command-line interface to operate Vision yourself. Use MCP to give an agent access to the same supported product operations. MCP is the connection protocol between the host and Vision; it is not another app account or a separate search service.

The installed commands and tool identifiers still use `indra` and `zortex`. Use those names as shown even though this handbook calls the product Vision.

## Start with one operation

### Terminal

Check the installed version and current sources:

```sh
indra --version
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"sources"}'
```

Replace the path with your existing Vault directory. If the installed `zortex` command is bound to that Vault, `zortex manage --json '{"what":"sources"}'` resolves it automatically. [CLI commands](/docs/vision/reference/cli) explains root selection and command differences.

### Agent host

The equivalent MCP operation is `indra.manage` with:

```json
{"what":"sources"}
```

Read the result, choose the relevant source, then discover its operations. A source list is not a claim that every source is connected.

## Reference map

### [CLI commands](/docs/vision/reference/cli)

Open the app, connect a source, inspect status, or run an Action yourself.

### [Set up MCP](/docs/vision/reference/mcp-setup)

Connect an agent host to an existing installation.

### [MCP tools](/docs/vision/reference/mcp-tools)

Tool arguments and local versus remote availability.

### [Shared Actions](/docs/vision/reference/actions)

Fixed connection, browser, sync, and sharing operations.

### [SQL reference](/docs/vision/reference/sql)

Working queries over retained records.

### [Remote access](/docs/vision/reference/remote-access)

Reach your computer from another client.

## Read a result before continuing

Most product operations return a result object with `ok`, `empty`, or `err`. The value inside `ok` may itself describe running work, a continuation, partial coverage, or an available catalog. Inspect that payload before deciding what happened.

| Result | Next step |
| --- | --- |
| Requested data or verified saved object | Use it to finish the task. |
| Job ID or browser continuation | Continue that same job or session. |
| Successful empty query | Check scope if unexpected; do not treat it as an authentication failure. |
| Partial collection | Preserve its reported scope and continuation. |
| Error | Follow its code and current state; verify an uncertain write before retrying. |

The terminal prints JSON. MCP returns the product result as structured content and text; a host may render it differently. An exit status, opened page, or outer success wrapper alone does not establish the requested business result.

## Match the installed capability

The handbook describes the intended experience and documents concrete supported routes. An older package may lack a command, tool, or web-handbook reader. Check `indra --help`, the host's actual tool list, and the returned method schema. Follow [Updates](/docs/vision/settings/updates) when a needed capability is unavailable.

Local and remote MCP expose different tool sets. Provider Actions are discovered from the installed connection; fixed product Actions are described in this reference and the installed `indra.instruction`. This reference does not announce a separate public HTTP API.
