Choose CLI and MCP operations
Discover every command and tool with exact signatures, permissions and boundaries.
The CLI is the broad public operating surface; its MCP server exposes a subset of the same registered operations. Authentication and authorization follow the saved credential, live platform role and selected target.
Establish context
Documentation browsing needs no login: start with farthershore docs ls, expand
a collection with farthershore docs tree backend-sdk, and retrieve a file with
farthershore docs read <path> --format json. See documentation traversal
for heading reads, search, and stage selection. Authentication below applies to
platform operations, not public docs retrieval.
Follow installation and login. Normal device login requires a human to allow the CLI to act as them. Selecting an organization changes routing context, not the user's authority. A separately issued MakerToken has its own restricted scope.
Inspect the installed version before copying a command:
farthershore --version
farthershore --help
farthershore operations list --format json
Use the global options for context and output configuration. Prefer structured output for automation. Never place raw credentials in command arguments.
Discover exact signatures
The sidebar's Complete reference group contains a page for every top-level command and every nested command, including local commands that are not platform operations. Generated help includes required arguments, flags, defaults and command-specific descriptions.
The platform catalog connects operation keys to ownership class, permission, CLI command, MCP tool and unavailable reason. Repository-authored and Git-triggered operations are documented boundaries. A catalog entry is not a promise that arbitrary REST access is supported.
Connect MCP
Run the farthershore-mcp binary as a stdio MCP server in the agent host. The MCP tool reference includes the exact input schema, side-effect annotation and one-time-secret behavior for each tool. Use the existing credential configuration; never put a credential in the MCP launch arguments.
Execute and verify
Read the relevant product guide before a write. Confirm the business and environment. Use dry-run when the command supports it, retain idempotency keys for retries, and obey the documented confirmation boundary. Read back state after success; an accepted asynchronous operation still needs convergence evidence.
If help differs from this reference, check the installed version against the catalog package versions. Do not guess a replacement flag or fall back to an undocumented endpoint.