If you already have an AI coding agent running (Claude Code, Cursor, Codex, …), paste this — the install guide bundled in the package has every remaining step (credentials, client config, the Claude Code plugin, restarting), so there's nothing else to keep in sync here:

Install the appknox-mcp MCP server for me:
1. `uv tool install --reinstall appknox-mcp` —
   **always include `--reinstall`**: without it, `uv` silently does nothing if
   any version is already installed, even a stale one missing this exact flag.
2. Run `appknox-mcp --install-guide` and follow it exactly.

That's it — the agent installs it, reads the guide, asks you for credentials, writes the config, and tells you to restart the client.

Prefer a deterministic install? Clone and run the installer — macOS, Linux, and Windows all get the identical flow and write identical config, just via a .sh or .ps1 wrapper around the same Python backend:

macOS / Linux / WSL / Git Bash:

git clone git@github.com:appknox/appknox-mcp.git
cd appknox-mcp
./scripts/install.sh

Windows (PowerShell):

git clone git@github.com:appknox/appknox-mcp.git
cd appknox-mcp
.\scripts\install.ps1

It installs uv if missing, auto-detects the MCP clients on your machine, and lets you pick which to configure (space-separated numbers, a for all, or m for manual steps). It prompts for your token (hidden input) and your base URL (no default offered — always ask, since white-labeled deployments use a different host), merges the server into each selected client's config without touching anything else, and git-ignores any token-bearing config. If Claude Code is selected, it also installs the plugin (claude plugin marketplace add + claude plugin install, user scope) so the /appknox:* slash commands and the fixer agent are available from any repo, not just this one. Then restart the client(s).

Name clients directly to skip detection: ./scripts/install.sh cursor codex (or .\scripts\install.ps1 cursor codex on Windows). Set APPKNOX_ACCESS_TOKEN / APPKNOX_BASE_URL beforehand to skip the prompts.

Full step-by-step, per-client config paths, and by-hand setup: INSTALL.md.

Run /mcp in any session — it's registered at user scope, so this works in any project, not just one repo — you should see appknox listed with ~9 tools. If you also installed the plugin, try /appknox:triage to confirm the slash commands loaded (this needs the plugin's own credentials — see INSTALL.md for the env-var export it relies on).

Fully quit (Cmd+Q) and reopen — it only reads config at launch. Then either:

• click the hammer/tools icon in the chat input and look for resolve_latest_file, list_analyses, etc., or
• click + below the chat box → Connectors, or
• go to Settings → Developer to see the server's status and logs.

Restart the Codex session, then run /mcp — appknox should appear in the server list.

Restart your copilot session, then run /mcp inside it — or run copilot mcp list directly from your shell. Either should show appknox.

Also run with --allow-all-mcp-server-instructions (v1.0.66+) if you want the guided workflow (resolve → triage → fix → verify, exploitability shown by default, etc.) — Copilot CLI doesn't feed any MCP server's instructions to the model without it, so without this flag it'll still call the tools correctly but skip the intended flow unless you spell each step out yourself.

Restart Cursor, then open Settings → MCP. appknox should show a green dot with a tool count next to it. (Green dot but 0 tools? Cursor caps tools at 40 across all enabled servers combined — check what else you have enabled.)

Restart Windsurf, then click the MCPs icon in the top-right of the Cascade panel — appknox should show a green status indicator with its tools listed underneath.

Reload the window (Command Palette → Developer: Reload Window), then Command Palette → MCP: List Servers — appknox should appear with start/stop/restart options. Once started, open Copilot Chat and check the tools icon next to the model picker — appknox's tools should be listed and toggled on there.