Telemetry

What's collected from the CLI and local MCP server

Ask your agent

Check whether Percher's usage statistics are on, and turn them off.Read the guide at percher.app/docs/telemetry

How it works, with exact details

Usage statistics from the Percher CLI and the local MCP server are off until you turn them on.

The first time you run a CLI command in a terminal, it asks: “Send anonymous usage statistics to Percher? (y/N)”. The answer is saved in ~/.percher/telemetry.json ($XDG_CONFIG_HOME/percher/ when set) and both clients follow it; with no answer within 20 seconds, it asks again next time. CI, AI agent terminals, scripts, --json runs and the MCP server never ask and send nothing until you say yes.

percher telemetry on
percher telemetry off
percher telemetry status

PERCHER_NO_TELEMETRY=1 (or true) or DO_NOT_TRACK=1 turns it off whatever the saved answer says.

When on, the CLI sends its version, the command name, success/error with an error type, OS, and Bun version.

The local MCP server (@percher/mcp) sends one event per tool call: package version, tool name, success/error with an error type, OS, Bun version, a random session id generated when the server starts, a short summary of known flags (such as dryRun or preview, or the number of env keys set, never their names or values), the call's duration and a tool-specific outcome such as live or failed.

No file names, source code, or env var names or values are collected. The random MCP session ID correlates tool-call events within that server session.

See our Privacy Policy for full details.