vijil-mcp

# vijil-mcp MCP (Model Context Protocol) server for the Vijil AI trust platform. Lets Claude Code interact with Vijil Console APIs through typed tools — using the CLI under the hood. ## How it works ``` Claude Code ←── stdio ──→ vijil-mcp (local process) ─── vijil-console CLI ──→ Vijil Console API ``` The MCP server is a **local process** on your machine — not a deployed server. Claude Code spawns it as a subprocess, discovers its tools automatically, and calls them during conversations. Each tool runs a `vijil-console` command and returns JSON output. ## Prerequisites - **Python 3.10+** - **A Vijil Console account** with API access - **Claude Code** (CLI, desktop app, or VS Code extension) ## Install ```bash pip install vijil-mcp # or isolated: pipx install --include-deps vijil-mcp ``` `--include-deps` is required for the `pipx` path — pipx only exposes a package's own console scripts by default, so a plain `pipx install vijil-mcp` leaves `vijil-console` (a dependency, not `vijil-mcp` itself) unreachable on PATH. The tradeoff: it also exposes every other dependency's scripts. This automatically installs `vijil-console` (the CLI) as a dependency. ## Upgrading an environment that predates this rename If this environment already has **both** `vijil-console` and `vijil-sdk` installed from before this rename (they used to collide on the `vijil` command and the `vijil_cli` package — see below), do **not** `pip install --upgrade` them in place, in either order. Fully uninstall both first, then reinstall: ```bash pip uninstall vijil-console vijil-sdk pip install --upgrade vijil-console vijil-sdk # or vijil-mcp, which pulls in vijil-console ``` Why: pre-rename, both packages wrote files to the same paths (the `vijil` script, and — before a companion vijil-sdk fix — the `vijil_cli` package directory), so each package's installed-files manifest (`RECORD`) still lists paths it no longer actually owns. An in-place upgrade of either package uninstalls its *o…