You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can optionally identify the end user on whose behalf requests are being made by setting the `TAVILY_HUMAN_ID` environment variable. When set, Tavily MCP forwards it as the `X-Human-Id` header on every API call, enabling per-user analytics.
212
+
213
+
This is **entirely optional** — leave it unset and behavior is unchanged.
214
+
215
+
```json
216
+
{
217
+
"mcpServers": {
218
+
"tavily-mcp": {
219
+
"command": "npx",
220
+
"args": ["-y", "tavily-mcp@latest"],
221
+
"env": {
222
+
"TAVILY_API_KEY": "your-api-key-here",
223
+
"TAVILY_HUMAN_ID": "your-user-id"
224
+
}
225
+
}
226
+
}
227
+
}
228
+
```
229
+
230
+
**Privacy note:** Tavily hashes `human_id` server-side (SHA-256) before storage, so the raw value is never persisted. Even so, prefer opaque identifiers (e.g. an internal user ID) over raw PII like emails when possible.
231
+
209
232
## Acknowledgments ✨
210
233
211
234
-[Model Context Protocol](https://modelcontextprotocol.io) for the MCP specification
0 commit comments