{"version":"2.1.302","anchor":"env-keys-for-tool-servers-tracked-separately","canonical_anchor":"env-keys-for-tool-servers-tracked-separately","heading":"Claude Code keeps a separate set of environment values for tool servers","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/env-keys-for-tool-servers-tracked-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Claude Code keeps a separate set of environment values for tool servers\n\nClaude Code now holds a separate, initially empty set of environment values for launching tool servers\n\n**Unclear.** What values go into the tool server environment, and when it is used, is not shown.\n\n**What**\n\nClaude Code now keeps a separate set of environment values for launching tool servers, the outside programs that supply extra tools. It starts empty and sits beside the set Claude Code already passes to programs it starts from your settings.\n\n**Why**\n\nTool servers may get their own launch environment, kept apart from the one other started programs receive.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}