Clarify token requirements for MCP integration#139
Conversation
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.
| ### 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 |
There was a problem hiding this comment.
I don't think this should be a part of the list if it doesn't work
There was a problem hiding this comment.
Hi @sgoedecke, I tried it - it works and also github/github-mcp-server#696 (comment)
There was a problem hiding this comment.
Oh nice! In that case, fix the merge conflicts and I'll approve.
There was a problem hiding this comment.
Conflicts are resolved 🙌🏼
There was a problem hiding this comment.
Looks like there's still a linting error with prettier
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Thanks for your patience! |
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.