### Setup Docmancer and agent integrations

Source: https://docmancer.dev/docs/cli-reference

Bootstraps the `docmancer.yaml` configuration file, initializes the local SQLite index, and installs one or more agent skills or instruction files. Use `--all` to install all integrations non-interactively, or `--agent` to specify individual agents.

```bash
docmancer setup [options]
```

--------------------------------

### docmancer setup

Source: https://docmancer.dev/docs/cli-reference

Bootstraps the Docmancer configuration, initializes the local SQLite index, and installs agent integrations.

```APIDOC
## docmancer setup

### Description
Create the local index and install selected agent integrations.

### Usage
```
docmancer setup [options]
```

### Notes
This bootstraps `docmancer.yaml`, initializes the local SQLite index, and installs one or more agent skill or instruction files.

### Options
#### `--all`
Install all agent integrations non-interactively.

#### `--agent <name>`
Install a specific agent (can be repeated).
```

--------------------------------

### Setup Docmancer

Source: https://docmancer.dev

Run 'docmancer setup' to register the local MCP entry for coding agents. This is a one-time setup that simplifies subsequent package installations and Docmancer state updates.

```bash
❯ docmancer setup
```

--------------------------------

### Install agent integrations

Source: https://docmancer.dev/docs/cli-reference

Installs the docmancer skill or instructions file for a specified coding agent. Run `docmancer setup` for the initial flow, or use this command to install or refresh individual agents.

```bash
docmancer install <agent> [options]
```

--------------------------------

### Non-interactive Docmancer Setup

Source: https://docmancer.dev/docs/installation

Installs all agent integrations non-interactively. This is useful for automated setups.

```bash
docmancer setup --all

```

--------------------------------

### Install Docmancer with pip

Source: https://docmancer.dev/docs/getting-started

A standard installation method for Docmancer using pip.

```bash
pip install docmancer

```

--------------------------------

### Install Docmancer Gemini Skill Project-Locally

Source: https://docmancer.dev/docs/gemini-integration

Installs the Docmancer skill within the current project directory at `.gemini/skills/docmancer/SKILL.md`. Use this for project-specific integrations.

```bash
docmancer install gemini --project

```

--------------------------------

### Install an API MCP pack

Source: https://docmancer.dev/docs/cli-reference

Installs a local API MCP pack. The installer checks the local cache, the hosted Docmancer artifact API, and falls back to source compilation for supported packs. Once installed, the pack is served from local files.

```bash
docmancer install-pack <package>@<version> [options]
```

--------------------------------

### Install Claude Desktop Skill with Docmancer

Source: https://docmancer.dev/docs/claude-desktop-integration

Use this command to create a zip package for uploading to Claude Desktop. This is the standard installation method for this integration.

```bash
docmancer install claude-desktop
```

--------------------------------

### Project-Local Installation for Agents

Source: https://docmancer.dev/docs/agent-integration

Installs the Docmancer skill or instructions file within the current project directory. This is useful for project-specific configurations or when versioning the configuration.

```bash
docmancer install claude-code --project

```

```bash
docmancer install gemini --project

```

```bash
docmancer install cline --project

```

```bash
docmancer install github-copilot --project

```

--------------------------------

### Run Docmancer Setup

Source: https://docmancer.dev/docs/getting-started

Execute this command to create the local configuration and register supported coding agents.

```bash
docmancer setup

```

--------------------------------

### List Installed Packs

Source: https://docmancer.dev/docs/api-mcp-packs

Lists all installed API MCP packs.

```bash
docmancer mcp list

```

--------------------------------

### Example docmancer.yaml Configuration

Source: https://docmancer.dev/docs/configuration

A comprehensive example of a docmancer.yaml file, demonstrating settings for index, query, and web_fetch configurations. Relative paths are resolved against the config file's directory.

```yaml
index:
  provider: sqlite
  db_path: ~/.docmancer/docmancer.db
  extracted_dir: ~/.docmancer/extracted

query:
  default_budget: 2400
  default_limit: 8
  default_expand: adjacent

web_fetch:
  workers: 8
  default_page_cap: 500

```

--------------------------------

### Install Pack with Expanded Tools

Source: https://docmancer.dev/docs/api-mcp-packs

Installs an API MCP pack including the full set of tools, not just the curated subset.

```bash
docmancer install-pack open-meteo@v1 --expanded

```

--------------------------------

### Install OpenCode Skill for Docmancer

Source: https://docmancer.dev/docs/opencode-integration

Installs the docmancer skill for OpenCode. This command installs the skill to two locations: a primary OpenCode skill path and a shared compatibility path.

```bash
docmancer install opencode
```

--------------------------------

### Example MCP Server Request

Source: https://docmancer.dev/docs/api-mcp-packs

The HTTP GET request dispatched by the agent to the local docmancer mcp serve process to fetch weather data.

```http
GET /v1/forecast?latitude=40.7812&longitude=-73.9665&current_weather=true

```

--------------------------------

### docmancer install

Source: https://docmancer.dev/docs/cli-reference

Installs the Docmancer skill or instructions file for a specified coding agent. Supports various agents and can install into project-level directories.

```APIDOC
## docmancer install

### Description
Install the docmancer skill or instructions file for a coding agent.

### Usage
```
docmancer install <agent> [options]
```

### Agents
`claude-code`, `claude-desktop`, `cline`, `cursor`, `codex`, `codex-app`, `codex-desktop`, `gemini`, `github-copilot`, `opencode`

### Notes
Run `docmancer setup` for the normal first-time flow. Use `docmancer install <agent>` when you want to install or refresh one agent manually.

### Options
#### `--project`
Install in project-level skills/instructions directory (Claude Code, Gemini, Cline, or GitHub Copilot).
```

--------------------------------

### Query Agent for Weather Information

Source: https://docmancer.dev/docs/getting-started

An example natural language query to an agent that utilizes installed API packs. The agent will select the appropriate API operation and call the local MCP runtime.

```bash
Get the current weather in New York Central Park.

```

--------------------------------

### Install Docmancer

Source: https://docmancer.dev/docs/api-mcp-packs

Installs the Docmancer CLI tool. Ensure you are using Python 3.13 or a compatible version.

```bash
pipx install docmancer --python 3.13

```

--------------------------------

### Start the Local MCP Server

Source: https://docmancer.dev

Launch the docmancer mcp serve command to start the local MCP server over stdio. This runtime reads local pack files and credentials for API calls, eliminating the need for a hosted execution service.

```bash
❯ docmancer mcp serve
```

--------------------------------

### Install Docmancer for Cursor

Source: https://docmancer.dev/docs/cursor-integration

Installs docmancer globally for Cursor integration. This sets up both a primary skill file and a fallback in AGENTS.md.

```bash
docmancer install cursor
```

--------------------------------

### Install Docmancer with pipx

Source: https://docmancer.dev/docs/getting-started

Use this command to install Docmancer with a specific Python version.

```bash
pipx install docmancer --python python3.13

```

--------------------------------

### Install Docmancer Browser Support

Source: https://docmancer.dev/docs/installation

Installs the optional Playwright dependency for browser-based fetching and downloads the Chromium browser.

```bash
pip install 'docmancer[browser]'
playwright install chromium

```

--------------------------------

### Install Project-Local Skills

Source: https://docmancer.dev/docs/project-config

Use the `--project` flag to install skills like Claude Code, Gemini, or Cline specifically for the current project. This is useful for project-specific availability or version control.

```bash
docmancer install claude-code --project
docmancer install gemini --project
docmancer install cline --project

```

--------------------------------

### Install a Docmancer MCP Pack

Source: https://docmancer.dev/docs/how-it-works

Installs a specified package version locally. Pack artifacts are cached or fetched from a hosted API. This command writes installed packs to `~/.docmancer/servers/` and updates the local manifest.

```bash
docmancer install-pack <package>@<version>
```

--------------------------------

### Install Docmancer Gemini Skill Globally

Source: https://docmancer.dev/docs/gemini-integration

Installs the Docmancer skill globally for use with Gemini CLI. This makes the skill available at `~/.gemini/skills/docmancer/SKILL.md` and `~/.agents/skills/docmancer/SKILL.md`.

```bash
docmancer install gemini

```

--------------------------------

### Install Docmancer Skills for Codex Variants

Source: https://docmancer.dev/docs/codex-integration

Use these commands to install the Docmancer skill for different Codex variants. Each command installs the skill to both the primary Codex path and a shared compatibility path.

```bash
docmancer install codex
docmancer install codex-app
docmancer install codex-desktop
```

--------------------------------

### Manage local API MCP runtime and installed packs

Source: https://docmancer.dev/docs/cli-reference

Commands for managing the local API MCP runtime and installed packs. Use `serve` for the stdio server, `list` to see installed packs, `doctor` to check health, and `enable`/`disable` to manage pack status.

```bash
docmancer mcp serve
```

```bash
docmancer mcp list
```

```bash
docmancer mcp doctor
```

```bash
docmancer mcp enable <package> [--version <version>]
```

```bash
docmancer mcp disable <package> [--version <version>]
```

--------------------------------

### Verify API Pack Installation

Source: https://docmancer.dev/docs/getting-started

Use this command to check the status and health of installed API packs, especially those requiring credentials.

```bash
docmancer mcp doctor

```

--------------------------------

### Install Docmancer for a Specific Agent

Source: https://docmancer.dev/docs/agent-integration

Installs the Docmancer skill for a particular agent. Ensure the agent name is supported.

```bash
docmancer install claude-code

```

--------------------------------

### Install Docmancer Cline Skill Globally

Source: https://docmancer.dev/docs/cline-integration

Installs the Docmancer skill globally for Cline. This makes the skill available system-wide.

```bash
docmancer install cline

```

--------------------------------

### Install an API Pack

Source: https://docmancer.dev/docs/getting-started

Installs a specified API MCP pack locally. This command also updates the local manifest and reports credential and safety requirements.

```bash
docmancer install-pack open-meteo@v1

```

--------------------------------

### Install Specific Docmancer Agents

Source: https://docmancer.dev/docs/installation

Installs integrations for specific agents, such as Claude Code and Cursor, or just GitHub Copilot.

```bash
docmancer setup --agent claude-code --agent cursor
docmancer setup --agent github-copilot

```

--------------------------------

### Add Documentation for Codex Querying

Source: https://docmancer.dev/docs/codex-integration

Index external documentation sources using this command before querying them with Codex. This example adds the pytest documentation.

```bash
docmancer add https://docs.pytest.org
```

--------------------------------

### Install a Version-Pinned API Pack

Source: https://docmancer.dev

Install a specific version of an API MCP pack, such as open-meteo@v1. This ensures agents call the exact version intended, and Docmancer manages local pack files and safety gates.

```bash
❯ docmancer install-pack open-meteo@v1
```

--------------------------------

### Install Docmancer Cline Skill Project-Local

Source: https://docmancer.dev/docs/cline-integration

Installs the Docmancer skill within the current project directory. Cline automatically discovers workspace-level skills when enabled.

```bash
docmancer install cline --project

```

--------------------------------

### Verify Docmancer Gemini Skill Installation

Source: https://docmancer.dev/docs/gemini-integration

Checks if the Docmancer skill is correctly installed and recognized by Gemini CLI. Look for the 'gemini' entry in the output.

```bash
docmancer doctor

```

--------------------------------

### docmancer install-pack

Source: https://docmancer.dev/docs/cli-reference

Installs a local API MCP pack from a specified package and version. It checks local cache, the hosted Docmancer artifact API, and falls back to source compilation for supported packs. Once installed, the pack is served locally.

```APIDOC
## docmancer install-pack

### Description
Install a local API MCP pack.

### Usage
```
docmancer install-pack <package>@<version> [options]
```

### Options
#### `--expanded`
Activate the full tool surface instead of the curated subset.

#### `--allow-destructive`
Permit destructive operations for this pack.

#### `--allow-execute`
Permit executor types such as Python import executors.
```

--------------------------------

### List Installed Docmancer MCP Packages

Source: https://docmancer.dev/docs/how-it-works

Displays installed packages, their enabled status, tool counts, and destructive-call mode. Useful for managing local tool packs.

```bash
docmancer mcp list
```

--------------------------------

### Verify Docmancer Skill Installation

Source: https://docmancer.dev/docs/codex-integration

Run this command after installation to confirm that the Docmancer skill is recognized by Codex. Check for 'codex' and 'codex-shared' entries with file paths.

```bash
docmancer doctor
```

--------------------------------

### docmancer mcp

Source: https://docmancer.dev/docs/cli-reference

Manages the local API MCP runtime and installed packs. This includes serving the runtime, listing installed packs, running diagnostics, and enabling/disabling specific packs.

```APIDOC
## docmancer mcp

### Description
Manage the local API MCP runtime and installed packs.

### Usage
```
docmancer mcp serve
docmancer mcp list
docmancer mcp doctor
docmancer mcp enable <package> [--version <version>]
docmancer mcp disable <package> [--version <version>]
```

### Notes
`docmancer mcp serve` is the stdio server that agents launch for API MCP packs. It is separate from the docs-retrieval skill workflow that calls `docmancer query`.
```

--------------------------------

### Remove an installed API MCP pack

Source: https://docmancer.dev/docs/cli-reference

Removes an installed API MCP pack from the local system. You can specify a version to remove a particular version of the pack.

```bash
docmancer uninstall <package>[@<version>]
```

--------------------------------

### Reinstall Docmancer Agent Skill

Source: https://docmancer.dev/docs/troubleshooting

If an agent does not pick up the Docmancer skill, reinstall it using `docmancer install <agent>`. Ensure the skill file path is correct and restart the agent's editor if necessary.

```bash
docmancer install <agent>

```

--------------------------------

### Manage Python Versions for Docmancer

Source: https://docmancer.dev/docs/troubleshooting

Docmancer requires Python 3.11-3.13. Check your current version with `python3 --version`. If needed, install a specific Python version using `pipx install`.

```bash
python3 --version

```

```bash
pipx install docmancer --python python3.13

```

--------------------------------

### Reset Index

Source: https://docmancer.dev/docs/configuration

Command to clear the index data while preserving the configuration settings. Use this to reset the search index without losing your setup.

```bash
docmancer remove --all

```

--------------------------------

### docmancer uninstall

Source: https://docmancer.dev/docs/cli-reference

Removes an installed API MCP pack from the local system.

```APIDOC
## docmancer uninstall

### Description
Remove an installed API MCP pack.

### Usage
```
docmancer uninstall <package>[@<version>]
```
```

--------------------------------

### Initialize Project Configuration

Source: https://docmancer.dev/docs/project-config

Run this command in your project directory to create a local docmancer.yaml file with default settings.

```bash
cd my-project
docmancer init

```

--------------------------------

### Search Available Tools

Source: https://docmancer.dev

Use docmancer_search_tools to discover available operations exposed by installed API packs. This allows agents to find specific versioned operations before dispatching a call.

```bash
❯ docmancer_search_tools
```

--------------------------------

### Fix 'Command Not Found: docmancer'

Source: https://docmancer.dev/docs/troubleshooting

Ensure the `docmancer` binary is on your PATH by checking pipx installations and ensuring the binary directory is included. Restart your terminal after making changes.

```bash
pipx list

```

```bash
pipx ensurepath

```

--------------------------------

### Resolve Pydantic/Binary Wheel Errors

Source: https://docmancer.dev/docs/troubleshooting

If installation errors occur due to Python architecture mismatches (e.g., on Apple Silicon), uninstall and reinstall Docmancer using the correct Python executable path.

```bash
pipx uninstall docmancer
pipx install docmancer --python /opt/homebrew/bin/python3

```

--------------------------------

### Uninstall Pack

Source: https://docmancer.dev/docs/api-mcp-packs

Removes an installed API MCP pack and its associated artifacts.

```bash
docmancer uninstall open-meteo@v1

```

--------------------------------

### docmancer doctor

Source: https://docmancer.dev/docs/cli-reference

Checks the Docmancer configuration, SQLite index, and installed agent skills for potential issues.

```APIDOC
## docmancer doctor

### Description
Check config, SQLite index, and installed agent skills.

### Usage
```
docmancer doctor
```
```

--------------------------------

### Verify Docmancer MCP Artifacts and Credentials

Source: https://docmancer.dev/docs/how-it-works

Checks artifact hashes, agent registration, and required credentials for installed MCP packs. Ensures the integrity and readiness of your local tool server.

```bash
docmancer mcp doctor
```

--------------------------------

### Initialize project-local docmancer.yaml

Source: https://docmancer.dev/docs/cli-reference

Creates a project-local `docmancer.yaml` configuration file. Use the `--dir` option to specify the target directory for the config file.

```bash
docmancer init [options]
```

--------------------------------

### Initialize Project-Local Config

Source: https://docmancer.dev/docs/configuration

Use this command to create a project-specific docmancer.yaml file in the current directory. This file takes precedence over the global configuration.

```bash
docmancer init

```

--------------------------------

### Run Docmancer Health Check

Source: https://docmancer.dev

Execute 'docmancer mcp doctor' to perform a health check on the Docmancer MCP setup. This verifies credentials, checks for gated destructive endpoints, and ensures all checks pass.

```bash
❯ docmancer mcp doctor
```

--------------------------------

### Add documentation from a URL or local path

Source: https://docmancer.dev/docs/cli-reference

Fetches and indexes documentation from a given URL or local path. Supports various providers and discovery strategies, with options to control the number of pages, browser usage, fetch workers, and index recreation.

```bash
docmancer add <url-or-path> [options]
```

--------------------------------

### Serve Docmancer MCP Tools Locally

Source: https://docmancer.dev/docs/how-it-works

Launches a local MCP server over stdio that reads local artifacts and exposes meta-tools for searching and calling tools. This keeps the startup process lean.

```bash
docmancer mcp serve
```

--------------------------------

### Query Documentation with Default Settings

Source: https://docmancer.dev/docs/examples

Queries indexed documentation using default settings, returning a compact markdown context pack with source attribution. The default token budget is 2400.

```bash
docmancer query "How do I parametrize a pytest fixture?"

```

--------------------------------

### docmancer init

Source: https://docmancer.dev/docs/cli-reference

Creates a project-local `docmancer.yaml` configuration file.

```APIDOC
## docmancer init

### Description
Create a project-local `docmancer.yaml` config file.

### Usage
```
docmancer init [options]
```

### Options
#### `--dir <path>`
Target directory for the config file.
```

--------------------------------

### Add Documentation from URL

Source: https://docmancer.dev/docs/adding-docs

Fetch and index documentation from a given URL. Docmancer automatically detects the documentation platform and applies the best fetching strategy.

```bash
docmancer add https://docs.example.com
```

--------------------------------

### Add Documentation from Local Files

Source: https://docmancer.dev/docs/adding-docs

Index documentation by pointing Docmancer to a local directory containing Markdown or text files.

```bash
docmancer add ./path/to/markdown/files
```

--------------------------------

### Fetch documentation from GitBook URL

Source: https://docmancer.dev/docs/cli-reference

Downloads documentation from a GitBook-style URL and saves it as local markdown files without indexing. Requires specifying the output directory using the `--output` flag.

```bash
docmancer fetch <url> --output <dir>
```

--------------------------------

### Add Documentation from GitHub Repository

Source: https://docmancer.dev/docs/adding-docs

Index documentation directly from a GitHub repository. Docmancer will extract README files and content from the docs directory.

```bash
docmancer add https://github.com/owner/repo
```

--------------------------------

### List indexed documentation sources

Source: https://docmancer.dev/docs/cli-reference

Displays a list of indexed documentation sources. Use the `--all` flag to show every stored page or file.

```bash
docmancer list [options]
```

--------------------------------

### Add Documentation URL for Retrieval

Source: https://docmancer.dev/docs/getting-started

Indexes documentation from a given URL locally. This allows agents to retrieve explanatory context when typed tools are not available.

```bash
docmancer add https://docs.example.com

```

--------------------------------

### Force Provider for URL Documentation

Source: https://docmancer.dev/docs/adding-docs

When adding documentation from a URL, you can explicitly specify the provider to ensure the correct fetching strategy is used.

```bash
docmancer add https://docs.example.com --provider mintlify
```

--------------------------------

### Expand Context to Include Full Page

Source: https://docmancer.dev/docs/querying

Include the full page content within your token budget when expanding context.

```bash
docmancer query "auth setup" --expand page

```

--------------------------------

### Update All Existing Documentation Sources

Source: https://docmancer.dev/docs/adding-docs

Re-fetch and re-index all previously added documentation sources to ensure they are up-to-date with any upstream changes.

```bash
docmancer update
```

--------------------------------

### Add Documentation Source

Source: https://docmancer.dev

Add a URL as a documentation source using 'docmancer add'. This indexes the content for retrieval when typed tools are unavailable.

```bash
❯ docmancer add https://docs.example.com
```

--------------------------------

### Add Documentation to Docmancer Index

Source: https://docmancer.dev/docs/gemini-integration

Indexes a given URL to make its documentation available for querying via Gemini. Ensure documentation is indexed before querying.

```bash
docmancer add https://docs.pytest.org

```

--------------------------------

### Basic Query

Source: https://docmancer.dev/docs/querying

Perform a basic search for a query string. Returns a compact markdown context pack with source attribution and estimated token savings.

```bash
docmancer query "How do I set up authentication?"

```

--------------------------------

### Query indexed documentation

Source: https://docmancer.dev/docs/cli-reference

Searches indexed documentation and returns a context pack based on a question. Options allow control over the maximum output tokens, number of sections, and expansion behavior.

```bash
docmancer query "<question>" [options]
```

--------------------------------

### Add Documentation with Browser Flag

Source: https://docmancer.dev/docs/installation

Use the `--browser` flag when adding documentation from JavaScript-heavy sites that require browser rendering.

```bash
docmancer add https://js-heavy-docs.example.com --browser

```

--------------------------------

### Query Documentation Index

Source: https://docmancer.dev/docs/getting-started

Queries the local documentation index for specific information. This is useful when an agent needs explanatory context not covered by typed tools.

```bash
docmancer query "How do I authenticate?"

```

--------------------------------

### docmancer fetch

Source: https://docmancer.dev/docs/cli-reference

Downloads documentation from a GitBook-style URL to local markdown files without indexing.

```APIDOC
## docmancer fetch

### Description
Download docs from a GitBook-style URL to local markdown files without indexing.

### Usage
```
docmancer fetch <url> --output <dir>
```
```

--------------------------------

### Query Local Documentation Index

Source: https://docmancer.dev/docs/how-it-works

Performs a BM25 search against the local SQLite FTS5 index to retrieve relevant documentation sections. Results are packed into a context pack constrained by a token budget. Use `--expand` to include adjacent sections or `--expand page` for full page content.

```bash
docmancer query
```

```bash
docmancer query --expand
```

```bash
docmancer query --expand page
```

--------------------------------

### Control Output Size with Token Budget

Source: https://docmancer.dev/docs/querying

Set a token budget to limit the amount of context returned in the results. The default budget is 2400 tokens.

```bash
docmancer query "auth setup" --budget 2000

```

--------------------------------

### Query Documentation with JSON Output

Source: https://docmancer.dev/docs/examples

Queries indexed documentation and returns the results in a structured JSON format, which is useful for piping into other tools.

```bash
docmancer query "pytest fixture scope" --format json

```

--------------------------------

### Query Documentation

Source: https://docmancer.dev

Use 'docmancer query' to retrieve context from indexed documentation sources. This is useful when agents need information that cannot be obtained through API tools.

```bash
❯ docmancer query "auth flow"
```

--------------------------------

### Enable Pack

Source: https://docmancer.dev/docs/api-mcp-packs

Enables a specific API MCP pack for a given version.

```bash
docmancer mcp enable open-meteo --version v1

```

--------------------------------

### docmancer add

Source: https://docmancer.dev/docs/cli-reference

Fetches and indexes documentation from a specified URL or local path, with options to force providers, discovery strategies, and control fetching behavior.

```APIDOC
## docmancer add

### Description
Fetch and index documentation from a URL or local path.

### Usage
```
docmancer add <url-or-path> [options]
```

### Options
#### `--provider`
Force provider: auto, gitbook, mintlify, web, github, crawl4ai. Default: `auto`.

#### `--strategy`
Force discovery strategy. Default: `auto`.

#### `--max-pages`
Maximum pages to fetch. Default: `500`.

#### `--browser`
Enable Playwright for JS-heavy sites. Default: `off`.

#### `--fetch-workers`
Concurrent page fetch workers. Default: `auto`.

#### `--recreate`
Drop and rebuild index for this source. Default: `off`.
```

--------------------------------

### Default Project Configuration Settings

Source: https://docmancer.dev/docs/project-config

This is the default content of a docmancer.yaml file created by `docmancer init`. It specifies paths for the local database and extracted files.

```yaml
index:
  db_path: .docmancer/docmancer.db
  extracted_dir: .docmancer/extracted/

```

--------------------------------

### Re-fetch and re-index documentation sources

Source: https://docmancer.dev/docs/cli-reference

Updates documentation sources by re-fetching and re-indexing them. You can specify a particular source to update or update all sources if no source is provided. Options include limiting the maximum pages to fetch and enabling browser usage for JavaScript-heavy sites.

```bash
docmancer update [source]
```

--------------------------------

### docmancer list

Source: https://docmancer.dev/docs/cli-reference

Displays a list of indexed documentation sources. The `--all` flag shows every stored page/file.

```APIDOC
## docmancer list

### Description
Show indexed documentation sources.

### Usage
```
docmancer list [options]
```

### Options
#### `--all`
Show every stored page/file.
```

--------------------------------

### Add Documentation URL for Retrieval

Source: https://docmancer.dev/docs/how-it-works

Adds a URL to Docmancer's local documentation index. The tool detects the platform and uses an appropriate fetching strategy. Use the `--browser` flag for JavaScript-heavy sites requiring rendering.

```bash
docmancer add <url>
```

```bash
docmancer add <url> --browser
```

--------------------------------

### Minimal Default Global Config

Source: https://docmancer.dev/docs/configuration

This is the minimal default configuration created automatically. It specifies paths for the index database and extracted files.

```yaml
index:
  db_path: ~/.docmancer/docmancer.db
  extracted_dir: ~/.docmancer/extracted/

```

--------------------------------

### Check Indexed Documents

Source: https://docmancer.dev/docs/troubleshooting

Verify if any documents are indexed by running `docmancer list`. If the list is empty, add documentation using `docmancer add`.

```bash
docmancer list

```

```bash
docmancer add https://docs.example.com

```

--------------------------------

### List Indexed Sources

Source: https://docmancer.dev/docs/examples

Lists all individual pages and files currently indexed by Docmancer.

```bash
docmancer list

```

```bash
docmancer list --all

```

--------------------------------

### Add GitHub Repository Documentation

Source: https://docmancer.dev/docs/examples

Adds a GitHub repository, such as Next.js, to Docmancer. Docmancer extracts README and docs directories.

```bash
docmancer add https://github.com/vercel/next.js

```

--------------------------------

### Version Control Ignore Settings

Source: https://docmancer.dev/docs/project-config

Add these paths to your .gitignore file to prevent the local Docmancer database and extracted files from being committed to version control.

```gitignore
.docmancer/docmancer.db
.docmancer/extracted/

```

--------------------------------

### Update a Specific Documentation Source

Source: https://docmancer.dev/docs/adding-docs

Update a single, specific documentation source by providing its URL. This re-fetches and re-indexes only that source.

```bash
docmancer update https://docs.example.com
```

--------------------------------

### Download Docs Without Indexing

Source: https://docmancer.dev/docs/examples

Downloads raw Markdown files from GitBook sources to a specified output directory without indexing them.

```bash
docmancer fetch https://docs.pytest.org --output pytest-docs

```

--------------------------------

### Expand Query Context to Full Pages

Source: https://docmancer.dev/docs/examples

Expands query results to include adjacent sections or full page content within the token budget, useful for more comprehensive context.

```bash
docmancer query "Next.js middleware" --expand

```

```bash
docmancer query "Next.js middleware" --expand page

```

--------------------------------

### Add Local Markdown Files

Source: https://docmancer.dev/docs/examples

Indexes local Markdown or text files directly from a specified directory. No network requests are made for local files.

```bash
docmancer add ./my-internal-docs

```

--------------------------------

### Remove documentation sources or clear index

Source: https://docmancer.dev/docs/cli-reference

Removes a specific documentation source or clears the entire index. Use `--all` to remove all indexed data.

```bash
docmancer remove <source>
```

```bash
docmancer remove --all
```

--------------------------------

### Allow Destructive Operations

Source: https://docmancer.dev/docs/api-mcp-packs

Reinstalls a pack, enabling destructive operations by explicitly opting in.

```bash
docmancer install-pack <pkg>@<version> --allow-destructive

```

--------------------------------

### Increase Token Budget for Complex Queries

Source: https://docmancer.dev/docs/examples

Increases the token budget for queries that require more context, allowing for more complex information retrieval.

```bash
docmancer query "OAuth 2.0 flow" --budget 3000

```

--------------------------------

### docmancer query

Source: https://docmancer.dev/docs/cli-reference

Searches indexed documentation and returns a context pack based on a natural language question, with options to control output token limits, section inclusion, and format.

```APIDOC
## docmancer query

### Description
Search indexed docs and return a context pack.

### Usage
```
docmancer query "<question>" [options]
```

### Options
#### `--budget`
Maximum estimated output tokens. Default: `2400`.

#### `--limit`
Maximum sections to return. Default: `auto`.

#### `--expand`
Include adjacent sections. Default: `off`.

#### `--expand page`
Include full page within budget. Default: `off`.

#### `--format`
Output format: markdown or json. Default: `markdown`.
```

--------------------------------

### Control Output Size with Section Limit

Source: https://docmancer.dev/docs/querying

Limit the number of sections returned in the query results.

```bash
docmancer query "auth setup" --limit 5

```

--------------------------------

### Output Results as JSON

Source: https://docmancer.dev/docs/querying

Retrieve query results in JSON format instead of the default markdown.

```bash
docmancer query "auth setup" --format json

```

--------------------------------

### Update a Specific Source

Source: https://docmancer.dev/docs/examples

Re-fetches and re-indexes a specific documentation source when upstream changes occur.

```bash
docmancer update https://docs.pytest.org

```

--------------------------------

### docmancer inspect

Source: https://docmancer.dev/docs/cli-reference

Shows statistics for the SQLite index and extracts location information.

```APIDOC
## docmancer inspect

### Description
Show SQLite index stats and extract locations.

### Usage
```
docmancer inspect
```
```

--------------------------------

### Rebuild Docmancer Index

Source: https://docmancer.dev/docs/troubleshooting

To fix stale or corrupted indexes, rebuild a specific source with `docmancer add --recreate` or clear all indexed content with `docmancer remove --all`.

```bash
docmancer add https://docs.example.com --recreate

```

```bash
docmancer remove --all

```

--------------------------------

### Update All Indexed Sources

Source: https://docmancer.dev/docs/examples

Updates and re-indexes all sources currently managed by Docmancer.

```bash
docmancer update

```

--------------------------------

### Inspect SQLite index stats

Source: https://docmancer.dev/docs/cli-reference

Shows statistics for the SQLite index and extracts location information. This command provides insights into the internal state of the documentation index.

```bash
docmancer inspect
```

--------------------------------

### docmancer update

Source: https://docmancer.dev/docs/cli-reference

Re-fetches and re-indexes specified documentation sources, with options to control the maximum number of pages and browser usage.

```APIDOC
## docmancer update

### Description
Re-fetch and re-index documentation sources.

### Usage
```
docmancer update [source]
```

### Options
#### `--max-pages`
Maximum pages to fetch. Default: `500`.

#### `--browser`
Enable Playwright for JS-heavy sites. Default: `off`.
```

--------------------------------

### Expand Context to Include Adjacent Sections

Source: https://docmancer.dev/docs/querying

Include adjacent sections around matches to provide more surrounding context for the query results.

```bash
docmancer query "auth setup" --expand

```

--------------------------------

### Call a Specific Tool

Source: https://docmancer.dev

Utilize docmancer_call_tool to execute a specific API operation, providing the necessary endpoint and parameters. This is used after an agent has identified the correct operation via search.

```bash
❯ docmancer_call_tool
```

--------------------------------

### Remove a Specific Source

Source: https://docmancer.dev/docs/examples

Removes a specific documentation source from Docmancer's index.

```bash
docmancer remove https://docs.pytest.org

```

--------------------------------

### docmancer remove

Source: https://docmancer.dev/docs/cli-reference

Removes a specific documentation source or clears the entire index.

```APIDOC
## docmancer remove

### Description
Remove a source or clear the entire index.

### Usage
```
docmancer remove <source>
docmancer remove --all
```
```

--------------------------------

### Disable Pack

Source: https://docmancer.dev/docs/api-mcp-packs

Disables a specific API MCP pack for a given version.

```bash
docmancer mcp disable open-meteo --version v1

```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.