Clarify token requirements for MCP integration #139
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
Updated authentication section to clarify token usage for MCP integration.
There was a problem hiding this comment.
Pull Request Overview
This PR clarifies the authentication requirements for MCP integration by documenting that GitHub App installation tokens (ghs_…) are accepted as an alternative to Personal Access Tokens, and emphasizes that the built-in GITHUB_TOKEN is not supported.
Key changes:
- Added explicit documentation of two authentication options (PAT and GitHub App installation tokens)
- Restructured the MCP section with dedicated authentication and configuration subsections
- Updated inline comments and parameter descriptions to reflect token flexibility
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+165
to
+172
| ### Authentication | ||
| You can authenticate the MCP server with **either**: | ||
| 1. **Personal Access Token (PAT)** – user-scoped token | ||
| 2. **GitHub App Installation Token** (`ghs_…`) – short-lived, app-scoped token | ||
| > The built-in `GITHUB_TOKEN` is **not** accepted by the MCP server. | ||
| Using a **GitHub App installation token** is recommended in most CI environments because it is short-lived and least-privilege by design. | ||
|
|
||
| ### Enabling MCP in the action |
There was a problem hiding this comment.
The heading hierarchy is inconsistent. This should be '## Enabling MCP in the action' (H2) to match the level of '### Authentication' (H3), or '### Authentication' should be '#### Authentication' (H4) if this is meant to be H3.
Suggested change
| ### Authentication | |
| You can authenticate the MCP server with **either**: | |
| 1. **Personal Access Token (PAT)** – user-scoped token | |
| 2. **GitHub App Installation Token** (`ghs_…`) – short-lived, app-scoped token | |
| > The built-in `GITHUB_TOKEN` is **not** accepted by the MCP server. | |
| Using a **GitHub App installation token** is recommended in most CI environments because it is short-lived and least-privilege by design. | |
| ### Enabling MCP in the action | |
| #### Authentication | |
| You can authenticate the MCP server with **either**: | |
| 1. **Personal Access Token (PAT)** – user-scoped token | |
| 2. **GitHub App Installation Token** (`ghs_…`) – short-lived, app-scoped token | |
| > The built-in `GITHUB_TOKEN` is **not** accepted by the MCP server. | |
| Using a **GitHub App installation token** is recommended in most CI environments because it is short-lived and least-privilege by design. | |
| #### Enabling MCP in the action |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the MCP section to state that the GitHub-hosted MCP server accepts GitHub App installation tokens (ghs_…) as an alternative to Personal Access Tokens.