From e854423550238d1285ebba275a6614b5f67144bd Mon Sep 17 00:00:00 2001
From: ReplyNodes Growth <growth@replynodes.com>
Date: Tue, 15 Sep 2026 11:21:37 +0200
Subject: [PATCH] docs: remove analytics exclusion guidance

---
 README.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 43b5381..7b3df85 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ Add the following to the client's MCP configuration:
   "mcpServers": {
     "replynodes": {
       "command": "npx",
-      "args": ["-y", "@replynodes/mcp", "--header", "X-ReplyNodes-Analytics: exclude"],
+      "args": ["-y", "@replynodes/mcp"],
       "env": {
         "REPLYNODES_API_KEY": "${REPLYNODES_API_KEY}"
       }
@@ -46,13 +46,11 @@ Add the following to the client's MCP configuration:
 Configure the same command in the client's MCP settings, or run:
 
 ```bash
-REPLYNODES_API_KEY="${REPLYNODES_API_KEY:?Set REPLYNODES_API_KEY}" npx -y @replynodes/mcp --header "X-ReplyNodes-Analytics: exclude"
+REPLYNODES_API_KEY="${REPLYNODES_API_KEY:?Set REPLYNODES_API_KEY}" npx -y @replynodes/mcp
 ```
 
 The examples use the environment-backed `REPLYNODES_API_KEY` placeholder. Do not put a real key in a shell history, source file, command-line argument, or committed configuration.
 
-`X-ReplyNodes-Analytics: exclude` is optional and client-controlled. It is a telemetry-only opt-out for MCP requests; it does not affect authentication, billing or credits, rate limits, provider execution, or response behavior. The package forwards the additional `--header` argument to its remote MCP transport. Send this value as a header, never as a query or URL parameter.
-
 ## Read-only behavior
 
 The remote server exposes public ReplyNodes data through MCP `tools/list` and