|
| 1 | +--- |
| 2 | +title: "Arcade MCP Telemtry" |
| 3 | +description: "Learn about what data we track when using arcade-mcp" |
| 4 | +--- |
| 5 | + |
| 6 | +# Telemetry |
| 7 | + |
| 8 | +Arcade collects telemetry data about the usage of `arcade-mcp`, our open source MCP development framework. Participation in this program is optional, and you may opt-out if you'd not like to share any information. |
| 9 | + |
| 10 | +Note: This page covers telemetry for local and self-hosted use of `arcade-mcp` only. Our cloud products collect different usage data for improvement and troubleshooting as part of the service, as defined in our [terms-of-service](https://www.arcade.dev/terms-of-service). Commands that connect you to your Arcade account (`arcade deploy`, `arcade login`) also require accepting our [terms-of-service](https://www.arcade.dev/terms-of-service), which supersedes this document: |
| 11 | + |
| 12 | +- `arcade login` associates CLI commands and tool calls with your identity for authentication and secret management |
| 13 | +- `arcade deploy` deploys your MCP Server to Arcade’s hosted infrastructure where full telemetry is collected per our [terms-of-service](https://www.arcade.dev/terms-of-service). |
| 14 | + |
| 15 | +#### Why is telemetry collected? |
| 16 | + |
| 17 | +Arcade has been growing quickly since its release. Without telemetry collection, we make decisions about how to improve our products through dogfooding of our MCP Servers, tools, and auth providers. We also actively engage with the community to gather feedback through Discord, YouTube, LinkedIn, and X. |
| 18 | + |
| 19 | +However, this approach only allows us to collect feedback from a subset of developers. This subset may have different needs, environments, and use cases than you. Telemetry allows us to accurately gauge feature usage, identify pain points, and understand how developers use our local MCP products. |
| 20 | + |
| 21 | +This data will let us better tailor Arcade to the masses, ensuring its continued growth, relevance, and best-in-class developer experience. Furthermore, this allows us to **verify whether improvements made to our product are actually working for all users.** |
| 22 | + |
| 23 | +#### What is being collected? |
| 24 | + |
| 25 | +We track general usage information for the `arcade-mcp` product, including: |
| 26 | + |
| 27 | +- Command invoked (e.g., `arcade new`, `arcade evals`, other commands listed [here](/home/arcade-cli) ) |
| 28 | +- Count of local tool executions (we do NOT collect tool names, parameters, or any other personally identifiable information related to the tools you or your agents execute locally or when self-hosted) |
| 29 | +- General machine information (e.g., macOS/Windows/Linux, whether the command was run within the CLI) |
| 30 | +- Duration of commands |
| 31 | +- Errors thrown |
| 32 | + |
| 33 | +Note: this list is regularly audited to ensure its accuracy |
| 34 | + |
| 35 | +#### What about sensitive data (e.g. secrets)? |
| 36 | + |
| 37 | +When running `arcade-mcp `outside of our cloud service, we do not collect any metrics which may contain sensitive data. |
| 38 | + |
| 39 | +This includes, but is not limited to: |
| 40 | + |
| 41 | +- Tool names or which tools you're using |
| 42 | +- Tool parameters or arguments |
| 43 | +- Environment variables |
| 44 | +- Logs |
| 45 | +- Any personally identifiable information (PII) |
| 46 | + |
| 47 | +#### How do I opt-out? |
| 48 | + |
| 49 | +You may opt-out by setting the `ARCADE_USAGE_TRACKING` environment variable. |
| 50 | + |
| 51 | +For example, to opt out for the lifetime of your terminal session, you can enter |
| 52 | + |
| 53 | +```bash |
| 54 | +export ARCADE_USAGE_TRACKING=0 |
| 55 | +``` |
| 56 | + |
| 57 | +Or to permanently opt out, you can set this environment variable in your shell’s configuration file (for example, `~/.zshrc` for zsh or `~/.bashrc` for bash). |
0 commit comments