docs: use Claude MCP env option in Docker examples - #3220
Open
pentaoa wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #3032.
The Claude Code CLI documents
--env KEY=valuefor environment variables passed to a local MCP server. The Docker examples used the Copilot-style-eshorthand before the command separator, which Claude rejects as an unknown option.This updates all three Claude Docker examples to use
--envwhile leaving Docker's own-earguments after--unchanged.Validation
claude mcp add github -eexamples remain in the guide.git diff --checkAI assistance was used to locate the affected examples and cross-check the CLI syntax. I reviewed the final documentation diff.