Update docs

Author: JoannaaKL

README.md

@@ -342,14 +342,21 @@ If you don't have Docker, you can use `go build` to build the binary in the
 
 The `github-mcp-server` binary includes a few CLI subcommands that are helpful for debugging and exploring the server.
 
-- `github-mcp-server tool-search "<query>"` searches tools by name, description, and input parameter names.
-- Use `--max-results` to return more matches.
-- Output is colorized when writing to a TTY (and typically not colorized when piped).
-
+- `github-mcp-server tool-search "<query>"` searches tools by name, description, and input parameter names. Use `--max-results` to return more matches.
 Example:
 
 ```bash
-github-mcp-server tool-search "owner" --max-results 5
+github-mcp-server tool-search "issue" --max-results 5
+```
+
+- `github-mcp-server list-scopes` lists required OAuth scopes for the currently enabled tools/toolsets.
+
+List required OAuth scopes for enabled tools:
+
+```bash
+github-mcp-server list-scopes
+github-mcp-server list-scopes --toolsets=repos,issues,pull_requests
+github-mcp-server list-scopes --output=json
 ```
 
 ## Tool Configuration
@@ -868,7 +875,7 @@ The following sets of tools are available:
     - 'add' - add a sub-issue to a parent issue in a GitHub repository.
     - 'remove' - remove a sub-issue from a parent issue in a GitHub repository.
     - 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.
-    				 (string, required)
+         (string, required)
   - `owner`: Repository owner (string, required)
   - `replace_parent`: When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional)
   - `repo`: Repository name (string, required)
@@ -1096,8 +1103,8 @@ The following sets of tools are available:
 
 - **pull_request_read** - Get details for a single pull request
   - **Required OAuth Scopes**: `repo`
-  - `method`: Action to specify what pull request data needs to be retrieved from GitHub. 
-    Possible options: 
+  - `method`: Action to specify what pull request data needs to be retrieved from GitHub.
+    Possible options:
      1. get - Get details of a specific pull request.
      2. get_diff - Get the diff of a pull request.
      3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.

docs/installation-guides/README.md

@@ -3,7 +3,6 @@
 This directory contains detailed installation instructions for the GitHub MCP Server across different host applications and IDEs. Choose the guide that matches your development environment.
 
 ## Installation Guides by Host Application
-
 - **[GitHub Copilot in other IDEs](install-other-copilot-ides.md)** - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
 - **[Antigravity](install-antigravity.md)** - Installation for Google Antigravity IDE
 - **[Claude Applications](install-claude.md)** - Installation guide for Claude Web, Claude Desktop and Claude Code CLI
@@ -29,36 +28,32 @@ This directory contains detailed installation instructions for the GitHub MCP Se
 | Copilot in Eclipse | ✅ | ✅ Full (OAuth + PAT) | Local: Docker or Go build, GitHub PAT<br>Remote: Eclipse Plug-in for Copilot 0.10.0+ | Easy |
 
 **Legend:**
-
 - ✅ = Fully supported
 - ❌ = Not yet supported
 
-**Note:** Remote MCP support requires host applications to register a GitHub App or OAuth app for OAuth flow support – even if the new OAuth spec is supported by that host app. Currently, only VS Code has full remote GitHub server support.
+**Note:** Remote MCP support requires host applications to register a GitHub App or OAuth app for OAuth flow support – even if the new OAuth spec is supported by that host app. Currently, only VS Code has full remote GitHub server support. 
 
 ## Installation Methods
 
 The GitHub MCP Server can be installed using several methods. **Docker is the most popular and recommended approach** for most users, but alternatives are available depending on your needs:
 
 ### 🐳 Docker (Most Common & Recommended)
-
 - **Pros**: No local build required, consistent environment, easy updates, works across all platforms
 - **Cons**: Requires Docker installed and running
 - **Best for**: Most users, especially those already using Docker or wanting the simplest setup
 - **Used by**: Claude Desktop, Copilot in VS Code, Cursor, Windsurf, etc.
 
 ### 📦 Pre-built Binary (Lightweight Alternative)
-
 - **Pros**: No Docker required, direct execution via stdio, minimal setup
 - **Cons**: Need to manually download and manage updates, platform-specific binaries
 - **Best for**: Minimal environments, users who prefer not to use Docker
 - **Used by**: Claude Code CLI, lightweight setups
 
 ### 🔨 Build from Source (Advanced Users)
-
 - **Pros**: Latest features, full customization, no external dependencies
 - **Cons**: Requires Go development environment, more complex setup
 - **Prerequisites**: [Go 1.24+](https://go.dev/doc/install)
-- **Build command**: `go build -o github-mcp-server ./cmd/github-mcp-server`
+- **Build command**: `go build -o github-mcp-server cmd/github-mcp-server/main.go`
 - **Best for**: Developers who want the latest features or need custom modifications
 
 ### Important Notes on the GitHub MCP Server
@@ -70,11 +65,9 @@ The GitHub MCP Server can be installed using several methods. **Docker is the mo
 ## General Prerequisites
 
 All installations with Personal Access Tokens (PAT) require:
-
 - **GitHub Personal Access Token (PAT)**: [Create one here](https://github.com/settings/personal-access-tokens/new)
 
 Optional (depending on installation method):
-
 - **Docker** (for Docker-based installations): [Download Docker](https://www.docker.com/)
 - **Go 1.24+** (for building from source): [Install Go](https://go.dev/doc/install)
 
@@ -91,7 +84,6 @@ Regardless of which installation method you choose, follow these security guidel
 ## Getting Help
 
 If you encounter issues:
-
 1. Check the troubleshooting section in your specific installation guide
 2. Verify your GitHub PAT has the required permissions
 3. Ensure Docker is running (for local installations)
@@ -101,8 +93,8 @@ If you encounter issues:
 ## Configuration Options
 
 After installation, you may want to explore:
-
 - **Toolsets**: Enable/disable specific GitHub API capabilities
 - **Read-Only Mode**: Restrict to read-only operations
 - **Dynamic Tool Discovery**: Enable tools on-demand
 - **Lockdown Mode**: Hide public issue details created by users without push access
+