[docs] docs: unbloat getting-started-mcp guide#20136
Merged
Conversation
Remove ~70 lines of duplicate and verbose content: - Drop redundant "Common toolset combinations" table (covered by Available Toolsets below) - Condense Operating Modes from two full YAML examples to a two-sentence summary with a reference link - Remove Read-Only Mode section (a constraint, not an actionable configuration) - Remove Example 2 (PR Review), which was nearly identical to Example 1 - Merge "Registry-based Configuration" subsection into "Adding Servers" - Simplify Next Steps intro and trailing paragraph Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
bot
added
automation
documentation
pelikhan
approved these changes
Mar 9, 2026
Contributor
|
/q configure firewall to allow localhost |
Contributor
There was a problem hiding this comment.
Pull request overview
Reduces duplication and verbosity in the “Getting Started with MCP” guide while preserving essential guidance via tighter wording and reference links.
Changes:
- Removed redundant toolset and workflow examples to reduce repeated content.
- Condensed Operating Modes and Read-Only guidance into brief summaries with links to the full reference docs.
- Simplified “Next Steps” and merged/removed minor sub-sections for a shorter, more scannable guide.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| ``` | ||
|
|
||
| Write operations are handled through [safe outputs](/gh-aw/reference/safe-outputs/), which execute in a separate, permission-controlled job after the agent completes. | ||
| The GitHub MCP server always operates read-only. Write operations are handled through [safe outputs](/gh-aw/reference/safe-outputs/), which run in a separate permission-controlled job. |
There was a problem hiding this comment.
Minor grammar: “always operates read-only” reads awkwardly. Consider “always operates in read-only mode” for clarity/consistency with the linked reference docs.
Suggested change
| The GitHub MCP server always operates read-only. Write operations are handled through [safe outputs](/gh-aw/reference/safe-outputs/), which run in a separate permission-controlled job. | |
| The GitHub MCP server always operates in read-only mode. Write operations are handled through [safe outputs](/gh-aw/reference/safe-outputs/), which run in a separate permission-controlled job. |
This was referenced Mar 9, 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.
Removes ~70 lines of duplicate and verbose content from
docs/src/content/docs/guides/getting-started-mcp.md(324 → 255 lines, 21% reduction).Changes made
All essential information is preserved — the Operating Modes section now links to the full reference in github-tools, and the remaining two practical examples still demonstrate different use cases (issue triage vs. multi-service security audit).
Screenshots
Screenshots could not be captured: the Playwright browser runs in a network-sandboxed container that cannot reach the local preview server (connection timed out on both
localhost:4321and the host network interface). The documentation build succeeds normally and the page structure/links are intact.References: