Command line and configuration

wield-mcp init, doctor, check, demo and speed; config.json and environment variables.

All commands come with the npm package. After init, there's also a shortcut, ~/.wield/bin/wield, that runs the installed copy (on Windows %USERPROFILE%\.wield\bin\wield.cmd).

Command	What it does
`npx -y wield-mcp init`	Installs Wield into `~/.wield`, registers the bridge with your browsers, and asks app by app whether to add Wield (with backups). Waits for the extension, then runs `check`
`npx -y wield-mcp doctor`	Checks every link: Node, bridge launcher, browser registration, extension connection and version, recipes, signatures, account, policy, AI apps. Prints a fix for each problem
`npx -y wield-mcp check`	First-run check: one live, read-only sample through your browser. Ends with "Wield is ready"
`npx -y wield-mcp demo`	Runs three sites and then prints every host your computer contacted, from the logs
`npx -y wield-mcp speed`	Times `find_recipe` and `run` the way an agent does (p50 and p90). Read recipes only; `--runs N`, `--json file`, or name recipe ids
`wield-mcp` (no arguments)	The MCP server itself. Your AI app starts it

init options:

--yes: answer yes to every prompt.
--no-wait: don't wait for the extension.
--registry <url>: use another registry.
--recipes <dir>: development only. Use local recipe files instead of the registry.

~/.wield/config.json

json

{
  "registry_url": "https://wield.run/api/v1",
  "telemetry": false,
  "country": "DE",
  "api_key": "wld_…"
}

Key	Default
`registry_url`	`https://wield.run/api/v1`
`telemetry`	`false`	`true` sends `{recipe_id, version, ok, duration_ms, error_code}` per run, nothing else
`country`	From your time zone, then your locale	Two letters. Ranking prefers sites in this country
`api_key`	none	Pro or Team key from your wield.run dashboard (teams). Only ever sent to an `https://` registry
`telemetry_identified`	`false`	With `telemetry` on: send the API key with each report, so it counts for recipe health. This ties reports to your workspace

The file is created with mode 0600. Keep your API key here or in your AI app's environment, not in shared files.

Environment variables

Variable	Overrides
`WIELD_API_KEY`	`api_key`
`WIELD_REGISTRY_URL`	`registry_url`
`WIELD_TELEMETRY`	`telemetry` (`1` or `0`)
`WIELD_COUNTRY`	`country`
`WIELD_HOME`	The `~/.wield` folder
`WIELD_RECIPES_DIR`	Development: read recipes from a folder (unsigned) instead of the registry. The extension runs them only with Developer mode on (Wield popup → Developer), and every non-GET request asks for Allow
`WIELD_REGISTRY_KEYS`	Self-hosted registries and tests: extra trusted signing keys, JSON `{kid: public_key}`. `doctor` warns when it's set

#~/.wield/config.json

#Environment variables

~/.wield/config.json

Environment variables