docs: improve Claude installation guide with Windows PowerShell support#2312
Merged
Conversation
- Fix README.md: Remove non-existent 'Claude Web' from description - Add Windows PowerShell environment variable example for loading PAT from .env file The previous documentation only showed bash syntax for loading environment variables from .env files, which doesn't work on Windows PowerShell. This adds a PowerShell equivalent to help Windows users set up the GitHub MCP Server correctly.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Claude installation documentation to more accurately reflect supported Claude clients and to add a Windows PowerShell example for configuring the GitHub PAT when using Claude Code’s claude mcp add-json command.
Changes:
- Remove the inaccurate “Claude Web” mention from the installation-guides index.
- Add a Windows PowerShell example for loading
GITHUB_PATfrom a.envfile and using it in theclaude mcp add-jsoncommand.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/installation-guides/README.md | Updates the Claude Applications description to remove “Claude Web”. |
| docs/installation-guides/install-claude.md | Adds a PowerShell snippet for reading GITHUB_PAT from .env and using it in a claude mcp add-json call. |
FuzzysTodd
approved these changes
Apr 10, 2026
FuzzysTodd
approved these changes
Apr 10, 2026
SamMorrowDrums
previously approved these changes
May 30, 2026
Collaborator
SamMorrowDrums
left a comment
SamMorrowDrums
left a comment
There was a problem hiding this comment.
Pure docs addition — adds a Windows PowerShell variant alongside the existing bash example for sourcing GITHUB_PAT from .env. Helpful for Windows users, doesn't touch any existing instructions. LGTM.
- Linux/macOS: actually set GITHUB_PAT instead of inlining via subshell, matching the heading. - PowerShell: use Select-Object -First 1, split with max 2 parts, and trim quotes/whitespace so common .env formats work. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
SamMorrowDrums
approved these changes
May 30, 2026
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
This PR improves the Claude installation guide by:
Fixing inaccurate description: Removes 'Claude Web' from the README.md description since the install-claude.md document only covers Claude Desktop and Claude Code CLI (Claude Web doesn't have MCP server support).
Adding Windows PowerShell support: The previous documentation only showed bash syntax for loading environment variables from .env files. This adds a PowerShell equivalent to help Windows users correctly configure their GitHub PAT when setting up the GitHub MCP Server.
Changes
Why This Matters
Windows users previously had to translate bash commands to PowerShell syntax themselves, which could lead to configuration errors. The new PowerShell example uses proper escaping and follows PowerShell best practices for reading .env files.