Install

toolprint is one engine with five doors. Every route below ends at the same two verbs: scan (read-only verify) and pin (write toolprint.lock after review). Node.js 20 or newer is the only runtime requirement; Claude Desktop supplies its own Node.

Claude Desktop

1. Download toolprint-0.4.1.mcpb (checksums are on the release page).
2. Open the file and confirm Install, or drag it into Settings → Extensions.
3. Optionally set Default project directory in the extension settings — where relative paths and toolprint.lock discovery start.
4. Ask Claude to scan a project's MCP config. Pass a workingDirectory when the project is not the configured default.

The bundle includes the compiled server and its dependencies; nothing is fetched at run time.

Claude Code

In a current Claude Code session, one line installs from this repository's marketplace:

/plugin install toolprint --marketplace jestatsio/toolprint

Then confirm installation. From the shell, the equivalent two steps are:

claude plugin marketplace add jestatsio/toolprint
claude plugin install toolprint@toolprint

You get the toolprint MCP server (scan, pin), the toolprint skill, and the /scan and /pin commands. The plugin launches the server as npx -y toolprint@0.4.1 serve, pinned to an exact npm version.

Codex

Register this repository as a marketplace once, then add the plugin:

codex plugin marketplace add jestatsio/toolprint
codex plugin add toolprint@toolprint

Or download toolprint-0.4.1-marketplace.zip, unzip it, and run codex plugin marketplace add ./toolprint-marketplace against the extracted folder. Restart Codex and ask it to scan this project's MCP servers.

Any MCP host

toolprint is listed in the community MCP ecosystem as a standard stdio server. The generic config is:

{
  "mcpServers": {
    "toolprint": {
      "command": "npx",
      "args": ["-y", "toolprint@0.4.1", "serve"]
    }
  }
}

Set TOOLPRINT_WORKDIR in the server environment to give scans a default project directory. Credentials for authenticated remote servers you scan belong in the environment too (TOOLPRINT_BEARER, TOOLPRINT_HEADER_<NAME>) — see Authentication.

CLI

No install is required:

npx toolprint scan ./.vscode/mcp.json

Or install globally with npm install -g toolprint. Start with Get started.

GitHub Action

- uses: jestatsio/toolprint@v1
  with:
    config: ./.vscode/mcp.json
    fail-on: high

SARIF, PR comments, and baselines are covered in CI.

Verify the install

Whichever door you chose, a first scan of the clean example should pass. Through an agent: ask it to run a toolprint scan of your project config and report whether the result is failing. Through the CLI: npx toolprint scan inside a project exits 0 when clean, 2 when findings gate, 1 when a server cannot be reached.