> ## Documentation Index > Fetch the complete documentation index at: https://docs.tokenfactory.nebius.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuration Detailed configuration options for Contree MCP. ## Authentication The MCP server supports both auth modes the Contree API exposes — the same two `contree-cli` recognises: * **IAM (recommended).** Token + Project header. Sends `Authorization: Bearer ` and `Project: `. Default URL: `https://api.tokenfactory.nebius.com/sandboxes`. Use this for new deployments; the standard `NEBIUS_API_KEY` / `NEBIUS_AI_PROJECT` env vars are honoured. * **JWT (legacy).** Token only. Sends `Authorization: Bearer `. Used by the `contree.dev` PoC deployment. No project required. A profile’s `type = iam | jwt` line picks the scheme; the client class that issues backend requests is wired accordingly at startup. ### Profile File (Recommended) `contree-mcp` reads the same profile file that [`contree-cli`](https://docs.contree.dev/cli/tutorial/installation.html) writes, so a single login covers both tools. Install the CLI and run `contree auth`: ```bash theme={null} uv tool install contree-cli # or: pip install contree-cli contree auth # interactive setup ``` This writes `~/.config/contree/auth.ini` with mode `0600`. Override the directory with `CONTREE_HOME`. The file is INI-format with one `[profile:]` section per credential set and a `[DEFAULT] profile = ` line selecting the active profile: ```ini theme={null} [DEFAULT] profile = default [profile:default] type = iam url = https://api.tokenfactory.nebius.com/sandboxes token = project = [profile:staging] type = jwt url = https://contree.dev token = ``` Switch profiles persistently with `contree auth switch `, or per-invocation with `--profile ` / `CONTREE_PROFILE=`. `type = iam` requires `project`; `type = jwt` does not. ### Environment Variables (Per-Invocation Overrides) For one-off overrides without touching the profile file: ```bash theme={null} export CONTREE_TOKEN="your-token-here" export CONTREE_URL="https://api.tokenfactory.nebius.com/sandboxes" export CONTREE_PROJECT="your-nebius-project-id" ``` The standard Nebius IAM credentials are recognised too: ```bash theme={null} export NEBIUS_API_KEY="your-iam-key" export NEBIUS_AI_PROJECT="your-nebius-project-id" ``` #### Precedence (important) Field-by-field, highest first: 1. **CLI flags** — `--token`, `--project`, `--url`, `--profile`. 2. **`CONTREE_*` env vars** — `CONTREE_TOKEN` / `CONTREE_PROJECT` / `CONTREE_URL` / `CONTREE_PROFILE`. MCP-specific; always layered on top of the profile. 3. **`NEBIUS_*` env vars** — `NEBIUS_API_KEY` + `NEBIUS_AI_PROJECT`, recognised **only when both are set** (a complete IAM credential). A lone `NEBIUS_API_KEY` set ambiently for the Nebius SDK or terraform provider is **ignored**, and the MCP server logs an `info` line explaining why. 4. **Active profile** from `auth.ini`. Picked by, in order, `--profile` → `CONTREE_PROFILE` → the file’s `[DEFAULT] profile = ...`. Some practical implications: * `contree-mcp` (no args) loads the active profile, even if your shell has `NEBIUS_API_KEY` set for other tools. * `CONTREE_TOKEN=NEW contree-mcp` rotates the token but reuses the profile’s `project` and `url` — handy for short-lived tokens. * `contree-mcp --token X --project Y` populates token + project from the CLI; `url` and `auth_type` still come from the loaded profile unless `--url` / `--auth-type` are also supplied. * With no profile loaded and an incomplete `CONTREE_TOKEN` / `--token`, the server stops with “No API token configured” rather than running with half-set credentials. Token resolution order, per field: ``` token --token > CONTREE_TOKEN > NEBIUS_API_KEY* > profile.token project --project > CONTREE_PROJECT > NEBIUS_AI_PROJECT* > profile.project url --url > CONTREE_URL > profile.url > IAM default (IAM only) ``` `*` `NEBIUS_*` are read only when both are set. Tokens passed via env may appear in process listings — prefer the profile file for routine use. ## Server Options | Option | Environment Variable | Default | Description | | ------------------ | ------------------------- | ---------------------------------------------------------- | ------------------------------------------------------ | | - | `CONTREE_HOME` | `$XDG_CONFIG_HOME/contree` (typically `~/.config/contree`) | Directory containing `auth.ini` and MCP state | | `--profile` | `CONTREE_PROFILE` | active profile from `auth.ini` | Profile to use | | `--token` | `CONTREE_TOKEN` | from profile | API token (overrides profile) | | `--url` | `CONTREE_URL` | from profile | API base URL (overrides profile) | | `--project` | `CONTREE_PROJECT` | from profile | Project ID for IAM auth | | `--mode` | - | `stdio` | `stdio` or `http` | | `--http-port` | - | `9452` | HTTP mode port | | `--http-listen` | - | `127.0.0.1` | HTTP mode bind address | | `--log-level` | - | `warning` | Logging level | | `--version` / `-V` | - | - | Print the User-Agent the server emits and exit | | - | `CONTREE_NO_UPDATE_CHECK` | unset | Disable the daily PyPI update check (set to any value) | ## Cache Configuration | Option | Default | | -------------------- | ------------------------------------------------------------------------- | | `--cache-files` | `$CONTREE_HOME/mcp/files.db` (typically `~/.config/contree/mcp/files.db`) | | `--cache-general` | `$CONTREE_HOME/mcp/cache.db` (typically `~/.config/contree/mcp/cache.db`) | | `--cache-prune-days` | `60` | ## Client Configuration Examples With credentials stored in `~/.config/contree/auth.ini`, MCP client configs are minimal: ### Claude Code ```bash theme={null} claude mcp add --transport stdio contree -- $(which uvx) contree-mcp ``` ### HTTP Mode For network access from other machines: ```bash theme={null} contree-mcp --mode http --http-port 9452 --http-listen 0.0.0.0 ``` Visit `http://localhost:9452/` for interactive documentation with setup guides, tool reference, and best practices. Contree MCP Server HTTP interface ## Manual Installation ```bash theme={null} # Using uv uv pip install contree-mcp # Using pip pip install contree-mcp # Container environments (PEP 668) pip install --break-system-packages contree-mcp ```