Tool

`command`

The remote control. Commands follow the same shape as the command line — command words, then explicit options — so anything you can do at a terminal you can do here, and the other way round.

You ask your agent “is the repoql host healthy, and has it finished indexing?” — this is what it sends. The same words are the shell command, because the tool is the command line.

Your agent calls — mcp

command("host status")

You call — cli

rql host status

What comes back — the same on both surfaces

Host: 1.6.41 (56e59fc3) · pid 48181 · up 12m 51s … binary path and signed-in account Phase: Idle Ready: true Gates: queryable=true, searchable=true, ready=true Files: total=121901, pending=0, failed=0, stale=0 Semantic: ready=true, percent=100, enabled=true, fidelity=semantic Clients: 10 active · idle window 15m (pinned while attached)

Ten clients on one index — agents and terminals sharing a host that knows exactly what state it is in. Start with command("help"), which lists everything available; <command> --help gives usage for one.

Parameters

Parameter		What it does
command	required	The command and its options, as one string — `"config set --key search.rerankEnabled --value true"`.

The families

Family	What it covers
host	Status, restart, reindex a glob — the lifecycle of the process holding the index.
config	List, read, and set configuration keys.
account	Who you are signed in as, and the cloud entitlements that follow from it.
import	List and manage what is currently in the graph.
diagnostics	Memory, health, and the internals when something is wrong.
dashboard	Open the live view of the index and its work.

This page names what exists. The depth behind every name ships inside the binary at help:///: the bounds, the failure modes, how they compose. It answers to explore and read exactly like your code does. Install it, and your agent has the manual.