Skip to main content
Percher is still being built and account creation is paused — get notified when it opens.
Percher

Telemetry

What's collected from the CLI and local MCP server

Ask your agent
Turn off Percher's usage tracking for me.Read the guide at percher.app/docs/telemetry
How it works, with exact details

The Percher CLI sends anonymous usage statistics to help us improve the platform: CLI version, 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. The same opt-out variables apply to both.

Opt out by setting an environment variable:

PERCHER_NO_TELEMETRY=1    # or
DO_NOT_TRACK=1

See our Privacy Policy for full details.