Skip to content

Conversation

@joeyorlando
Copy link
Contributor

@joeyorlando joeyorlando commented Jan 27, 2026

Summary

  • Updated the GitHub MCP server access token description to clarify that either classic or fine-grained Personal Access Tokens work
  • Added the required scopes: repo, read:packages, read:org
  • Added a direct link to GitHub's token creation page

Fixes archestra-ai/archestra#1906

Update the access token description for the GitHub MCP server to
specify that either a classic or fine-grained Personal Access Token
is acceptable, along with the required scopes (repo, read:packages,
read:org) and a link to create one.

Fixes #1906

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Copilot AI review requested due to automatic review settings January 27, 2026 00:41
@vercel
Copy link

vercel bot commented Jan 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Review Updated (UTC)
archestra Ignored Ignored Jan 27, 2026 9:36am

Request Review

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves the GitHub MCP server configuration by clarifying the type of access token required and documenting the necessary permissions.

Changes:

  • Updated the access token description to specify that both classic and fine-grained Personal Access Tokens are supported
  • Added documentation of required OAuth scopes: repo, read:packages, read:org
  • Included a direct link to GitHub's token creation page for user convenience

@joeyorlando joeyorlando changed the title fix: clarify GitHub token type and required scopes fix: clarify GitHub remote MCP server token type, required scopes, and docs URL Jan 27, 2026
@joeyorlando joeyorlando merged commit ff3c62c into main Jan 27, 2026
11 checks passed
@joeyorlando joeyorlando deleted the fix/clarify-github-token-type branch January 27, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify required GitHub token type (fine-grained vs. classic)

1 participant