GitHub MCP Remote Server Tools Report - February 2026 #13106
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-08T13:19:55.432Z.
|
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.
-
Generated: February 1, 2026
MCP Mode: Remote
Toolsets: All
Previous Report: January 6, 2026
Executive Summary
pkg/workflow/data/github_toolsets_permissions.jsonInconsistency Detection
Toolset Integrity Checks
✅ All tools are properly categorized with no detected inconsistencies.
Expected Duplicate Tools (cross-repository search capability):
search_issuesappears in bothissues(single-repo) andsearch(cross-repo) toolsetssearch_pull_requestsappears in bothpull_requests(single-repo) andsearch(cross-repo) toolsetsJSON Mapping Comparison
Discrepancies Between MCP Server and JSON Mapping
Summary:
Extra Tools (in MCP but not in JSON)
These tools were listed in the JSON mapping but don't actually exist in the GitHub MCP remote server:
Action: ✅ Created pull request with updated JSON mapping (branch: update-github-mcp-tools-mapping-feb-2026)
Changes Since Last Report
Report Comparison: January 6, 2026 → February 1, 2026
✅ No tools were added, removed, or moved in the actual MCP server since the last report.
The changes made in this report relate to correcting the JSON mapping file to match the actual MCP server capabilities, not changes to the MCP server itself.
Tools by Toolset
View Complete Tools Catalog (56 tools across 19 toolsets)
Context Toolset
Description: GitHub Actions context and environment
Permissions Required: None
Tool Count: 3
Repos Toolset
Description: Repository operations
Permissions Required: Read:
contents, Write:contentsTool Count: 10
Issues Toolset
Description: Issue management
Permissions Required: Read:
issues, Write:issuesTool Count: 4
Pull Requests Toolset
Description: Pull request operations
Permissions Required: Read:
pull-requests, Write:pull-requestsTool Count: 3
Actions Toolset
Description: GitHub Actions workflows
Permissions Required: Read:
actionsTool Count: 3
Code Security Toolset
Description: Code scanning alerts
Permissions Required: Read:
security-events, Write:security-eventsTool Count: 2
Dependabot Toolset
Description: Dependabot alerts
Permissions Required: Read:
security-eventsTool Count: 2
Discussions Toolset
Description: GitHub Discussions
Permissions Required: Read:
discussions, Write:discussionsTool Count: 4
Experiments Toolset
Description: Experimental features
Permissions Required: None
Tool Count: 0
Status:⚠️ Empty toolset - no tools currently available
Gists Toolset
Description: Gist operations
Permissions Required: None
Tool Count: 2
Labels Toolset
Description: Label management
Permissions Required: Read:
issues, Write:issuesTool Count: 2
Notifications Toolset
Description: Notification management
Permissions Required: None
Tool Count: 2
Orgs Toolset
Description: Organization operations
Permissions Required: None
Tool Count: 1
Projects Toolset
Description: GitHub Projects (requires PAT - not supported by GITHUB_TOKEN)
Permissions Required: None (PAT required)
Tool Count: 6
Secret Protection Toolset
Description: Secret scanning
Permissions Required: Read:
security-eventsTool Count: 2
Security Advisories Toolset
Description: Security advisories
Permissions Required: Read:
security-events, Write:security-eventsTool Count: 3
Stargazers Toolset
Description: Repository stars
Permissions Required: None
Tool Count: 1
Users Toolset
Description: User information
Permissions Required: None
Tool Count: 0
Status:⚠️ Empty toolset - no tools currently available (use
search_usersfrom search toolset)Search Toolset
Description: Advanced search across all of GitHub
Permissions Required: None
Tool Count: 6
Recommended Default Toolsets
Based on comprehensive analysis of available tools and their usage patterns, the following toolsets are recommended as defaults when no toolset is specified:
Recommended Defaults:
context,repos,issues,pull_requests,searchRationale
context: Provides essential environment information and GitHub Actions context
repos: Core repository operations needed by most workflows
contentsread permissionissues: Issue management is fundamental to project workflows
issuesread permissionpull_requests: Pull request operations are central to development workflows
pull-requestsread permissionsearch: Cross-repository search capabilities are highly valuable
Specialized Toolsets (Enable When Needed)
Toolset Configuration Reference
When configuring the GitHub MCP server in agentic workflows, you can enable specific toolsets:
Available toolset options:
context- GitHub Actions context and environmentrepos- Repository operationsissues- Issue managementpull_requests- Pull request operationsactions- GitHub Actions workflowscode_security- Code scanning alertsdependabot- Dependabot alertsdiscussions- GitHub Discussionsexperiments- Experimental features (empty)gists- Gist operationslabels- Label managementnotifications- Notification managementorgs- Organization operationsprojects- GitHub Projects (requires PAT)secret_protection- Secret scanningsecurity_advisories- Security advisoriesstargazers- Repository starsusers- User information (empty)search- Advanced searchall- Enable all toolsetsNotes and Observations
All tools are read-only: The current GitHub MCP remote server provides only read operations. No write/create/update/delete tools are available.
Empty toolsets: Two toolsets (
experimentsandusers) currently contain no tools. User search functionality is available via thesearch_userstool in thesearchtoolset.PAT requirement: The
projectstoolset requires a Personal Access Token (PAT) and is not supported by the standardGITHUB_TOKENused in GitHub Actions workflows.Cross-repository search: The
searchtoolset provides powerful cross-repository search capabilities that complement the single-repository scoped tools in other toolsets.Permission requirements: Many toolsets require specific GitHub permissions. Ensure your workflow's
GITHUB_TOKENhas appropriate permissions for the toolsets you enable.Documentation update: A comprehensive reference guide has been created at
.github/instructions/github-mcp-server.instructions.mdwith detailed information about all tools, authentication, configuration, and best practices.Methodology
pkg/workflow/data/github_toolsets_permissions.jsonResources
.github/instructions/github-mcp-server.instructions.mdpkg/workflow/data/github_toolsets_permissions.json/tmp/gh-aw/cache-memory/github-mcp-tools.jsonReferences:
Beta Was this translation helpful? Give feedback.
All reactions