Skip to content

Falconer CLI

Use the Falconer CLI when you want direct command-line access to Falconer documents. It is published on npm as @falconer/cli.

For AI clients, MCP is the primary setup path. Use the CLI for shell scripts, terminal workflows, and direct document operations.

Install the CLI:

Terminal window
npm install -g @falconer/cli

Sign in with OAuth:

Terminal window
falconer oauth login

This opens your browser for Falconer authentication. Your local credentials are stored at ~/.config/falconer/config.json.

Verify your signed-in account and active organization:

% falconer oauth status
Logged in as xll@falconer.com (org: Lilu's Organization)

Use the help command to list available commands and options:

Terminal window
falconer help
falconer <command> --help

Manage your session and organization:

Terminal window
falconer oauth status
falconer oauth org list
falconer oauth org set <org-id-or-name>

Search and read docs:

Terminal window
falconer search "runbooks"
falconer read <document-id-or-url>

Search results include document metadata and a preview. Use the returned id or a Falconer URL with falconer read.

% falconer search "runbooks"
---
title: Write runbooks
id: dg84gsb9oryxx2mwp5dp4f8e
visibility: shared
updated: 77d ago
---
# Write runbooks
Turn your codebase, Slack threads, and notes into step-by-step runbooks ready for the next incident or deployment. Falconer drafts the runbook from your actual systems so it reflects how things really work, not how someone remembered them.
## Prerequisites
...

Create or update docs:

Terminal window
falconer create -f runbook.md
falconer content replace <document-id> --old "staging-v1" --new "staging-v2"