> ## Documentation Index
> Fetch the complete documentation index at: https://linkly.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Using Linkly AI CLI
> Learn how to use Linkly AI CLI for greater flexibility and a more technical experience.
## Introduction to Linkly AI CLI
Linkly AI CLI is a command-line tool that connects to Linkly AI Desktop's MCP service, allowing you to search, browse, and read local documents from the terminal. It also serves as a bridge between AI Agents (such as Claude Desktop, Cursor) and Linkly AI.
Search your documents directly from the command line — ideal for developers
and power users
Run in stdio MCP mode, enabling Claude Desktop, Cursor, and other AI tools
to call Linkly AI
## Installation
Run in your terminal:
```bash theme={null}
curl -sSL https://updater.linkly.ai/cli/install.sh | sh
```
Or install via Homebrew:
```bash theme={null}
brew tap LinklyAI/tap
brew install linkly
```
Run in PowerShell:
```powershell theme={null}
irm https://updater.linkly.ai/cli/install.ps1 | iex
```
Install from [crates.io](https://crates.io/crates/linkly-ai-cli) (requires Rust toolchain):
```bash theme={null}
cargo install linkly-ai-cli
```
After installation, verify the installation:
```bash theme={null}
linkly --version
```
By default, the CLI discovers and connects to the local Linkly AI Desktop app
via `~/.linkly/port`. You can also connect to a remote device via LAN or the
cloud tunnel — see [Connection Modes](#connection-modes) below.
## Usage
The CLI follows a **search → grep or outline → read** progressive workflow: first search to find target documents, then use grep to find patterns or view the outline to understand the structure, and finally read the specific content. When the user describes a container ("in my Notion notes", "in my Dropbox papers folder") whose actual path is unknown, call `find-paths` before `search` to discover the path.
Every successful command output ends with a `[meta] now=2026-05-08T...Z` UTC
timestamp line (or a top-level `_meta.now` field in JSON mode). This is
metadata Desktop provides to AI assistants for computing relative dates like
"last month" — human users can ignore it; for scripting, you may want to
filter out the last line before further parsing.
### Check Connection Status
```bash theme={null}
linkly status
```
Returns the running status, version number, number of indexed documents, and indexing status of Linkly AI Desktop.
### Search Documents
```bash theme={null}
linkly search "keywords or phrases"
```
Searches your local documents and returns the most relevant results, including title, path, relevance score, and content snippet.
**Common parameters:**
```bash theme={null}
# Limit the number of results (default 20, max 50)
linkly search "API design" --limit 5
# Filter by document type
linkly search "meeting minutes" --type pdf,docx
# Output in JSON format (suitable for scripting)
linkly search "budget report" --json
# Limit by time window (Q3 2024 quarterly reports)
linkly search "quarterly report" --modified-after 2024-07-01 --modified-before 2024-09-30
# Sort by time ("the latest", "the earliest" — when there's no fixed window)
linkly search "weekly retro" --time-sort newest --limit 5
```
`--modified-after` / `--modified-before` accept ISO 8601 UTC: a bare date
`2024-01-01` (treated as `00:00:00Z`) or a full RFC 3339 timestamp
`2024-01-01T00:00:00Z`. `--time-sort` accepts `newest` / `oldest`; omit it to
keep the default BM25 + vector relevance order.
### View Document Outline
```bash theme={null}
linkly outline
```
Retrieves the structured outline and metadata of a document. `DOC_ID` is obtained from search results. You can view multiple documents at once:
```bash theme={null}
linkly outline id1 id2 id3
```
The outline feature works best with Markdown, DOCX, PowerPoint (PPTX), and EPUB documents, as their
heading structures can be parsed. For plain text or PDFs without bookmarks,
it's recommended to use the `read` command directly.
### Search Patterns in Documents
```bash theme={null}
linkly grep
```
Search for regex pattern matches within a single document. Use when you need to find specific text (terms, names, dates, identifiers, etc.):
```bash theme={null}
# Find a pattern in a document
linkly grep "useState" 456
# Case-insensitive with context lines
linkly grep "error|warning" 1044 -C 3 -i
# Count matches only
linkly grep "TODO" 591 --mode count
# Paginate matches (skip first 20, show next 20)
linkly grep "import" 302 --offset 20 --limit 20
```
### Read Document Content
```bash theme={null}
linkly read
```
Reads the full content of a document, outputting text with line numbers. For long documents, you can read in pages:
```bash theme={null}
# Start from line 50, read 100 lines
linkly read --offset 50 --limit 100
```
**Pagination strategy:** By default, 200 lines are read per request (max 500 lines). For long documents, adjust `--offset` to read progressively:
```bash theme={null}
linkly read --offset 1 --limit 200 # Lines 1-200
linkly read --offset 201 --limit 200 # Lines 201-400
linkly read --offset 401 --limit 200 # Lines 401-600
```
### Find Paths (find-paths)
```bash theme={null}
linkly find-paths --patterns
```
Fuzzy-matches keywords against the **file path** field of indexed documents, aggregates matches at folder granularity, and returns the top folder candidates. It is positioned as a helper for `search`: when the user names a container ("in my Notion notes", "in my Dropbox papers folder") but you don't know its on-disk path, call `find-paths` first, then pass a distinctive segment of the returned path to `search` as `--path-glob`. When a folder name contains glob metacharacters (`* ? [`), use the returned `path_glob` field directly — it is already escaped to match that folder literally.
**Two-step workflow:**
```bash theme={null}
# Step 1: locate the real path
linkly find-paths --patterns Notion,notion --limit 5
# Suppose it returns .../Documents/Notion-Export-abc/workspace (1240 files)
# Step 2: search within that container
linkly search "shopping receipt" --path-glob "*Notion-Export*"
```
**Variant matching:** `--patterns` takes a comma-separated list of keywords, OR-matched against the path. **Pass several variants in one call** (translation pairs, casing, real app/SDK identifiers when known) to maximise first-pass recall:
```bash theme={null}
linkly find-paths --patterns Notion,notion,Notion-Export
linkly find-paths --patterns Slack,slack --library work-notes
```
`find-paths` is a "find folders" tool, not a "find files" tool: only matches
on **directory segments** count. If keywords match only the filename segment
(an "orphan file"), they are silently dropped. If a query returns zero folders
even though you expect matching files, fall back to calling `linkly search`
directly without `--path-glob`.
### MCP Mode
```bash theme={null}
linkly mcp
```
Runs as a stdio MCP server, exposing Linkly AI's tools to MCP-compatible AI clients.
**Configure Claude Desktop and other local AI apps:**
Add the following to the configuration file of Claude Desktop or similar apps:
Edit `~/.config/Claude/claude_desktop_config.json`:
```json theme={null}
{
"mcpServers": {
"linkly-ai": {
"command": "linkly",
"args": ["mcp"]
}
}
}
```
Edit `%APPDATA%\Claude\claude_desktop_config.json`:
```json theme={null}
{
"mcpServers": {
"linkly-ai": {
"command": "linkly",
"args": ["mcp"]
}
}
}
```
**Configure Cursor:**
In Cursor, open Settings → MCP Servers → Add Server, and add:
* Name: `linkly-ai`
* Command: `linkly mcp`
### Update CLI
```bash theme={null}
linkly self-update
```
Automatically checks for and updates to the latest version. The CLI also checks for updates in the background on each launch and will prompt you to run this command if a new version is available.
## Connection Modes
The CLI supports three ways to connect to your Linkly AI knowledge base:
| Mode | Flags | How it works |
| ---------- | ---------------------------------- | --------------------------------------------------------------- |
| **Local** | *(default, no flags needed)* | Auto-discovers the desktop app via `~/.linkly/port` |
| **LAN** | `--endpoint --token ` | Direct connection to another device on the local network |
| **Remote** | `--remote` | Connects via `https://mcp.linkly.ai` cloud tunnel using API Key |
### Local Mode (default)
No extra flags needed. The CLI reads `~/.linkly/port` to find the running desktop app:
```bash theme={null}
linkly search "machine learning"
linkly status
```
### LAN Mode
Connect to a Linkly AI instance running on another device in your local network. The token can be found in the desktop app under **Settings → MCP**:
```bash theme={null}
linkly search "report" --endpoint http://192.168.1.100:60606/mcp --token your_lan_token
linkly status --endpoint http://192.168.1.100:60606/mcp --token your_lan_token
```
### Remote Mode
Connect to your knowledge base from anywhere via the cloud tunnel. First, save your API key (from [linkly.ai/dashboard](https://linkly.ai/dashboard)):
```bash theme={null}
linkly auth set-key lkai_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```
Then use `--remote` with any command:
```bash theme={null}
linkly search "machine learning" --remote
linkly status --remote
```
`--endpoint` and `--token` are required together for LAN access. They cannot
be combined with `--remote`. For remote access, use `linkly auth set-key` to
save your API key.
## Parameter Reference
### Global Options
| Option | Scope | Description |
| ------------------ | ------------ | ---------------------------------------------------------------------------------------------- |
| `--endpoint ` | LAN | Connect to a specific MCP endpoint (e.g. `http://192.168.1.100:60606/mcp`), requires `--token` |
| `--token ` | LAN | Bearer token for LAN authentication (required with `--endpoint`, conflicts with `--remote`) |
| `--remote` | Remote | Connect via cloud tunnel at `https://mcp.linkly.ai` (conflicts with `--endpoint`) |
| `--json` | All commands | Output in JSON format (suitable for scripting and automation) |
| `-V, --version` | — | Display CLI version number |
| `-h, --help` | — | Display help information |
`--endpoint`, `--token`, and `--remote` are available on `search`, `grep`,
`outline`, `read`, and `status` commands. `--endpoint` alone (without
`--token`) is also available on the `mcp` command. `--json` is available on
all commands.
### search Parameters
| Parameter | Description | Default |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- |
| `` | Search keywords or phrase (required) | — |
| `--limit ` | Maximum number of results (1-50) | 20 |
| `--type ` | Filter by document type (comma-separated, e.g. `pdf,md,docx,epub`) | All |
| `--library ` | Restrict search to a specific library | — |
| `--path-glob ` | Filter by file path; substring-matched (may appear anywhere, no leading/trailing `*` needed). When the actual path is unknown, run `linkly find-paths` first | — |
| `--modified-after ` | Inclusive lower bound on modification time. ISO 8601 UTC: bare date `2024-01-01` or full `2024-01-01T00:00:00Z` | — |
| `--modified-before ` | Inclusive upper bound on modification time. Same format as `--modified-after` | — |
| `--time-sort ` | Time-based reordering: `newest` / `oldest`. Omit to keep relevance ordering | — |
### find-paths Parameters
| Parameter | Description | Default |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `--patterns ` | Comma-separated keyword list (required). Multiple keywords are OR-matched; pass several variants in one call (translation pairs, casing). Case-insensitive for ASCII; CJK is literal. | — |
| `--library ` | Restrict to a specific library | — |
| `--limit ` | Maximum number of candidate folders (1-50) | 10 |
### outline Parameters
| Parameter | Description | Default |
| --------- | ----------------------------------------- | ------- |
| `` | Document ID (required, supports multiple) | — |
### grep Parameters
| Parameter | Description | Default |
| -------------------- | ------------------------------------------------------------------------------------------------------- | ------- |
| `` | Regular expression pattern (required) | — |
| `` | Document ID to search (required) | — |
| `-C, --context` | Lines of context before and after | 3 |
| `-B, --before` | Lines of context before each match | — |
| `-A, --after` | Lines of context after each match | — |
| `-i` | Case-insensitive matching | — |
| `--mode` | Output mode: `content` or `count` | content |
| `--limit` | Maximum matches (max 100) | 20 |
| `--offset` | Number of matches to skip | 0 |
| `--fuzzy-whitespace` | Fuzzy whitespace matching: `true` to force on, `false` to force off, omit for auto (PDF on, others off) | auto |
### read Parameters
| Parameter | Description | Default |
| -------------- | --------------------------------- | ------- |
| `` | Document ID (required) | — |
| `--offset ` | Starting line number (from 1) | 1 |
| `--limit ` | Number of lines to read (max 500) | 200 |