feat: Update MCP docs with telemetry info (#2117)

<!-- CURSOR_SUMMARY -->
> [!NOTE]
> Adds telemetry documentation with opt-out instructions and fixes the
tools table for runs/storage entries.
> 
> - **Docs (MCP server)**
> - **Telemetry**: Add section detailing anonymous data collection,
default enablement, and opt-out methods for both remote
(`?telemetry-enabled=false`) and local stdio
(`--telemetry-enabled=false` or env) servers.
> - **Available tools table**: Fix and normalize entries for `runs` and
`storage` tools (`get-actor-run*`, `get-dataset*`,
`get-key-value-store*`), ensuring proper formatting and visibility.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c702337. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->



close: #2117

---------

Co-authored-by: Marcel Rebro <marcel.rebro@apify.com>

Author: jirispilka

sources/platform/integrations/ai/mcp.md

@@ -277,17 +277,17 @@ Use the UI configurator `https://mcp.apify.com/` to select your tools visually,
 | [`apify/rag-web-browser`](https://apify.com/apify/rag-web-browser) | Actor | ✅ | Browse and extract web data |
 | `search-apify-docs` | docs | ✅ | Search the Apify documentation for relevant pages |
 | `fetch-apify-docs` | docs | ✅ | Fetch the full content of an Apify documentation page by its URL |
-| `get-actor-run` | runs |  | Get detailed information about a specific Actor run |
-| `get-actor-run-list` | runs |  | Get a list of an Actor's runs, filterable by status |
-| `get-actor-log` | runs |  | Retrieve the logs for a specific Actor run |
-| `get-dataset` | storage |  | Get metadata about a specific dataset |
-| `get-dataset-items` | storage |  | Retrieve items from a dataset with support for filtering and pagination |
-| `get-dataset-schema` | storage |  | Generate a JSON schema from dataset items |
-| `get-key-value-store` | storage |  | Get metadata about a specific key-value store |
-| `get-key-value-store-keys`| storage |  | List the keys within a specific key-value store |
-| `get-key-value-store-record`| storage |  | Get the value associated with a specific key in a key-value store |
-| `get-dataset-list` | storage |  | List all available datasets for the user |
-| `get-key-value-store-list`| storage |  | List all available key-value stores for the user |
+| `get-actor-run` | runs | | Get detailed information about a specific Actor run |
+| `get-actor-run-list` | runs | | Get a list of an Actor's runs, filterable by status |
+| `get-actor-log` | runs | | Retrieve the logs for a specific Actor run |
+| `get-dataset` | storage | | Get metadata about a specific dataset |
+| `get-dataset-items` | storage | | Retrieve items from a dataset with support for filtering and pagination |
+| `get-dataset-schema` | storage | | Generate a JSON schema from dataset items |
+| `get-key-value-store` | storage | | Get metadata about a specific key-value store |
+| `get-key-value-store-keys` | storage | | List the keys within a specific key-value store |
+| `get-key-value-store-record` | storage | | Get the value associated with a specific key in a key-value store |
+| `get-dataset-list` | storage | | List all available datasets for the user |
+| `get-key-value-store-list` | storage | | List all available key-value stores for the user |
 | `add-actor`* | experimental | ❔ | Add an Actor as a new tool for the user to call |
 | `get-actor-output`* | - | ✅ | Retrieve the output from an Actor call which is not included in the output preview of the Actor tool. |
 
@@ -314,6 +314,49 @@ For a detailed overview of client support for dynamic discovery, see the [MCP cl
 
 :::
 
+## Telemetry
+
+The MCP server collects telemetry data about tool calls and MCP clients to help Apify understand usage patterns and improve the service.
+Participation in this program is optional and you may opt out if you prefer not to share any information.
+
+### Data collection
+
+All telemetry data is collected and stored securely.
+We do not collect any sensitive information such as conversations, arguments passed to tools, API tokens, or personal data.
+
+The server collects anonymous information about tool usage, including:
+
+- Basic information about used tools (calls, success/failure, duration)
+- MCP client attributes (client name, version, capabilities)
+
+By default, telemetry is _enabled_ for all tool calls.
+
+### Opt out of telemetry
+
+#### Remote server
+
+For the remote server (`mcp.apify.com`), you can opt out of telemetry by adding the `telemetry-enabled=false` query parameter to the server URL:
+
+```text
+https://mcp.apify.com?telemetry-enabled=false
+```
+
+#### Local stdio server
+
+For the local stdio server, opt out of telemetry using a CLI flag or an environment variable. When both the CLI flag and environment variable are set, the CLI flag takes precedence.
+
+- _CLI flag_: set the `--telemetry-enabled` CLI flag to `false`:
+
+  ```bash
+  npx @apify/actors-mcp-server --telemetry-enabled=false
+  ```
+
+- _Environment variable_: set the `TELEMETRY_ENABLED` environment variable to `false`:
+
+  ```bash
+  export TELEMETRY_ENABLED=false
+  npx @apify/actors-mcp-server
+  ```
 
 ## Advanced usage