Telemetry & Privacy

Website analytics

This website counts page views, installer clicks, copied install commands, and setup-guide choices. Only broad page, source, campaign, operating-system and client categories are sent to our own telemetry service. We do not store website visitor IDs, cookies, full URLs, search queries, referrer URLs, configuration files or credentials. Counts are retained for 90 days.

Do Not Track and Global Privacy Control turn off these events automatically. Your choice below is saved in this browser. Coarse campaign categories may be remembered in session storage for 30 minutes; they do not identify you or connect your browser visit to a local MCPProxy installation. Cloudflare processes network metadata and a short-lived rate-limit key to serve and protect these requests.

MCPProxy application telemetry

MCPProxy collects anonymous, aggregate usage statistics to help us understand how the product is used and where to focus improvements. Telemetry is entirely optional and can be disabled at any time.

We believe in full transparency. This page explains exactly what is collected, what is not, and how to opt out.

What is collected

MCPProxy sends a daily heartbeat containing only non-identifying, aggregate information:

Field	Example	Purpose
`anonymous_id`	`550e8400-...`	Random UUID for deduplication (not linked to you)
`version`	`0.21.3`	Track version adoption
`edition`	`personal`	Understand edition usage
`os`	`darwin`	Platform distribution
`arch`	`arm64`	Architecture distribution
`server_count`	`12`	Understand scale of usage
`connected_server_count`	`8`	Connection success rates
`tool_count`	`156`	Tool ecosystem size
`uptime_hours`	`47`	Usage patterns
`routing_mode`	`retrieve_tools`	Feature adoption
`quarantine_enabled`	`true`	Security feature adoption

What is NOT collected

The following is never collected or transmitted:

Server names, URLs, or configurations
Tool names or descriptions
API keys, tokens, or credentials
File paths or environment variables
IP addresses (stripped by our server before storage)
User identity, email, or account information
Tool call content, arguments, or responses
Any user-generated content

Anonymous ID

The anonymous ID is a random UUID (v4) generated on first run. It has no correlation to your hardware, user account, or identity. It exists solely to deduplicate heartbeats so the same installation is not counted twice in a single day.

You can reset it at any time by removing the telemetry.anonymous_id field from your config file. A new random ID will be generated on next startup.

How to opt out

There are three ways to disable telemetry. Pick whichever suits your workflow:

1. CLI (recommended)

mcpproxy telemetry disable

Verify the change:

mcpproxy telemetry status

Re-enable at any time:

mcpproxy telemetry enable

2. Configuration file

Edit ~/.mcpproxy/mcp_config.json:

{
  "telemetry": {
    "enabled": false
  }
}

3. Environment variable

export MCPPROXY_TELEMETRY=false

This overrides the config file setting and is useful for CI/CD environments or system-wide policies.

Data handling

Telemetry data is sent over HTTPS to a Cloudflare Worker.
Source IP addresses are stripped before storage.
Data is stored in Cloudflare D1 (EU region).
Data is used only for aggregate product analytics.
No third-party analytics services receive the data.

Open source

The telemetry implementation is fully open-source. You can audit every line of code that runs:

internal/telemetry/telemetry.go — heartbeat logic
internal/config/config.go — configuration (TelemetryConfig)

Last updated: March 2026. If you have questions about telemetry or privacy, please open an issue on GitHub.