GitHub MCP Remote Server Tools Audit - 2025-11-26 #4856
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 3 days ago. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The GitHub MCP remote server provides 72 tools organized across 19 toolsets, enabling AI agents to interact with GitHub's API through the Model Context Protocol. This audit validates the complete inventory of available tools, confirms the accuracy of internal JSON mappings, and verifies that no changes have occurred since the last audit on 2025-11-24.
Key Findings:
pkg/workflow/data/github_toolsets_permissions.jsoncontext,repos,issues,pull_requests,users) provide the right balance of functionality and minimal permissionsFull Report Details
Report Metadata
Generated: 2025-11-26
MCP Mode: Remote
Toolsets: All (19 toolsets)
Previous Report: 2025-11-24
Total Tools: 72
Changes Since Last Report: 0
Executive Summary
Tool Inventory Status
Validation Results
JSON Mapping Comparison
✅ 100% Accurate - The toolset-to-tools mapping in
pkg/workflow/data/github_toolsets_permissions.jsonperfectly matches the actual MCP server capabilities.Toolset Integrity Check
✅ All Clear - All 72 tools are properly categorized with no detected inconsistencies.
Tools by Toolset
Default Toolsets (21 tools)
These toolsets are enabled by default when
toolsets: [default]is specified or when no toolsets are configured.context - GitHub Actions Context (6 tools)
Description: User identity, teams, Copilot spaces, and GitHub documentation access
Required Permissions: None
get_copilot_spaceget_meget_team_membersget_teamsgithub_support_docs_searchlist_copilot_spacesrepos - Repository Operations (10 tools)
Description: Access repository content, commits, releases, and structure
Required Permissions:
contents(read)get_commitget_file_contentsget_latest_releaseget_release_by_tagget_repository_treeget_taglist_brancheslist_commitslist_releaseslist_tagsissues - Issue Management (3 tools)
Description: Read, list, and analyze GitHub issues
Required Permissions:
issues(read)issue_readlist_issue_typeslist_issuespull_requests - Pull Request Operations (2 tools)
Description: Access pull request details, diffs, files, and reviews
Required Permissions:
pull-requests(read)list_pull_requestspull_request_readusers - User Information (0 tools)
Description: User profile and information (placeholder for future expansion)
Required Permissions: None
Currently empty, reserved for future user-related operations
Specialized Toolsets (51 tools)
These toolsets should be enabled explicitly when needed for specific workflows.
actions - GitHub Actions Workflows (9 tools)
Required Permissions:
actions(read)download_workflow_run_artifactget_job_logsget_workflow_runget_workflow_run_logsget_workflow_run_usagelist_workflow_jobslist_workflow_run_artifactslist_workflow_runslist_workflowsWhen to use: CI/CD analysis, workflow debugging, build failure investigation
code_security - Code Scanning Alerts (2 tools)
Required Permissions:
security-events(read)get_code_scanning_alertlist_code_scanning_alertsWhen to use: Security analysis, code scanning review, vulnerability assessment
dependabot - Dependabot Alerts (2 tools)
Required Permissions:
security-events(read)get_dependabot_alertlist_dependabot_alertsWhen to use: Dependency management, security update workflows
discussions - GitHub Discussions (4 tools)
Required Permissions:
discussions(read)get_discussionget_discussion_commentslist_discussion_categorieslist_discussionsWhen to use: GitHub Discussions, community forums, Q&A sections
experiments - Experimental Features (0 tools)
Required Permissions: None
Currently empty, reserved for future experimental features
gists - Gist Operations (2 tools)
Required Permissions: None
get_gistlist_gistsWhen to use: Code snippet workflows, gist management
labels - Label Management (2 tools)
Required Permissions:
issues(read)get_labellist_labelWhen to use: Label management, issue/PR organization
notifications - Notification Management (2 tools)
Required Permissions: None
get_notification_detailslist_notificationsWhen to use: Notification management, inbox workflows
orgs - Organization Operations (1 tool)
Required Permissions: None
list_org_repository_security_advisoriesWhen to use: Organization-wide security advisory management
projects - GitHub Projects (6 tools)
Required Permissions:
repository-projects(read)get_projectget_project_fieldget_project_itemlist_project_fieldslist_project_itemslist_projectsWhen to use: GitHub Projects management, project board workflows
secret_protection - Secret Scanning (2 tools)
Required Permissions:
security-events(read)get_secret_scanning_alertlist_secret_scanning_alertsWhen to use: Secret scanning review, security workflows
security_advisories - Security Advisories (3 tools)
Required Permissions:
security-events(read)get_global_security_advisorylist_global_security_advisorieslist_repository_security_advisoriesWhen to use: Security advisory management, vulnerability research
stargazers - Repository Stars (1 tool)
Required Permissions: None
list_starred_repositoriesWhen to use: Repository popularity analysis, star management
search - Advanced Search (6 tools)
Required Permissions: None
search_codesearch_issuessearch_orgssearch_pull_requestssearch_repositoriessearch_usersWhen to use: Cross-repository search, broad discovery workflows
Recommended Default Toolsets
The current defaults (
context,repos,issues,pull_requests,users) remain optimal based on this audit.Why These Defaults?
contents,issues, andpull-requestsread permissionsCoverage Analysis
Configuration Reference
Basic Configuration
Custom Toolset Selection
Enable All Toolsets
Notes and Observations
Stability and Maturity
The GitHub MCP server has demonstrated excellent stability with zero changes over multiple days. This indicates a mature and reliable API surface that users can depend on.
Tool Distribution
repos(10),actions(9),context(6),projects(6),search(6)orgs(1),stargazers(1)experiments(0),users(0) - reserved for future usePermission Requirements
Tool Naming Patterns
Consistent conventions across all tools:
Methodology
pkg/workflow/data/github_toolsets_permissions.jsonDocumentation: Complete documentation is available in
.github/instructions/github-mcp-server.instructions.mdCache Location: Full report cached at
/tmp/gh-aw/cache-memory/github-mcp-tools-report-2025-11-26.mdBeta Was this translation helpful? Give feedback.
All reactions