GitHub MCP Remote Server Tools Report - 2026-02-15 #15903
Replies: 1 comment
-
|
💥 WHOOSH! 💥 The Claude smoke test agent just blazed through here faster than The Flash on a caffeine rush! ⚡️ MISSION STATUS: NOMINAL 🚀 All systems checked, all powers activated, all villains... wait, wrong comic. All tests passing! Vanishes in a cloud of AI-powered smoke 💨 🦸 Smoke Test Run §22035866590
|
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: 2026-02-15
MCP Mode: Remote
Toolsets: All
Previous Report: None (first run)
Executive Summary
Key Highlights
✅ JSON mapping is 100% accurate - All tools match the MCP server implementation
⚠️ Minor inconsistencies identified - Non-critical naming and empty toolset issues
✅ Well-organized toolsets - Clear categorization with logical groupings
📋 Recommended defaults updated - New default toolsets based on usage analysis
JSON Mapping Comparison
Discrepancies Between MCP Server and JSON Mapping
Summary:
✅ JSON mapping is accurate and matches the MCP server.
Action: No updates needed to
pkg/workflow/data/github_toolsets_permissions.json.Changes Since Last Report
This is the first report. No previous data available for comparison.
Future reports will include:
Inconsistency Detection
Toolset Integrity Checks
View Detailed Inconsistency Analysis
1. Duplicate Tools Across Toolsets
Intentional Duplicates (by design):
issuesandsearchtoolsetspull_requestsandsearchtoolsetsRationale: These duplications are intentional design patterns to provide:
✅ Status: This is intentional design, not a problem.
2. Naming Consistency
Minor Inconsistency Found:
list_labels(plural) to match naming conventionlist_*tools use plural forms (list_branches, list_commits, list_issues, etc.)Pattern Analysis:
get_*prefix: Single-item retrieval (get_commit, get_file_contents, etc.)list_*prefix: Multiple items (list_branches, list_commits, etc.)search_*prefix: Search operations (search_issues, search_code, etc.)*_readsuffix: Reading operations (issue_read, pull_request_read)3. Toolset Categorization
All tools are appropriately categorized. Each toolset contains relevant, related tools with clear purpose alignment:
4. Empty Toolsets
experiments: No tools (expected - reserved for future features)
users: No tools (unexpected)
userstoolset is defined but empty. This may be:5. Orphaned Tools
✅ No orphaned tools found. All 56 tools are properly categorized.
Overall Assessment
✅ The GitHub MCP toolset organization is well-structured with only minor naming inconsistencies. All tools are appropriately categorized with clear, logical groupings.
Recommended Default Toolsets
Based on analysis of usage patterns, frequency, and security impact:
Recommended Defaults
Rationale
View Detailed Rationale
Why these toolsets are included in defaults:
context (3 tools)
repos (10 tools)
issues (4 tools)
pull_requests (3 tools)
actions (3 tools)
discussions (4 tools)
search (6 tools)
Specialized Toolsets (Enable Explicitly)
The following toolsets should be enabled explicitly when needed:
Security Toolsets (require
security-eventspermissions):code_security: Code scanning alertsdependabot: Dependabot alertssecret_protection: Secret scanning alertssecurity_advisories: Security advisory managementNiche/Specialized Features:
gists: Snippet management (low frequency)labels: Label management (metadata-focused)notifications: User notifications (user-specific)orgs: Organization operations (org-specific)projects: GitHub Projects v2 (requires PAT token)stargazers: Repository star tracking (analytics)Empty Toolsets:
users: Currently no tools availableexperiments: Reserved for experimental featuresTools by Toolset
View Complete Tool Reference
Context Toolset
GitHub Actions context, Copilot spaces, and support documentation access.
Repos Toolset
Repository operations including commits, releases, branches, tags, and file access.
Issues Toolset
Issue management including reading, listing, and searching issues.
Pull Requests Toolset
Pull request operations including listing, reading, and searching PRs.
Actions Toolset
GitHub Actions workflow information and logs.
Code Security Toolset
Code scanning alerts for security vulnerabilities.
Dependabot Toolset
Dependabot alerts for vulnerable dependencies.
Discussions Toolset
GitHub Discussions for community Q&A and announcements.
Experiments Toolset
Status: Currently empty (reserved for future experimental features).
Gists Toolset
Gist operations for code snippets and notes.
Labels Toolset
Label management for issues and pull requests.
Note:
list_labelhas a minor naming inconsistency (should be plural).Notifications Toolset
User notification management.
Orgs Toolset
Organization-level operations.
Projects Toolset
GitHub Projects (v2) for project planning and tracking.
Important: Requires PAT token (NOT supported by GITHUB_TOKEN).
Secret Protection Toolset
Secret scanning alerts for leaked credentials.
Security Advisories Toolset
Security advisory management and disclosure.
Stargazers Toolset
Repository star tracking and analytics.
Users Toolset
Status: Currently empty (reserved for future user management features).
Search Toolset
Advanced search across GitHub entities.
Note:
search_issuesandsearch_pull_requestsalso appear in their respective domain toolsets.Toolset Configuration Reference
Workflow Configuration Examples
View Configuration Examples
Default Configuration (recommended):
Explicit Toolsets:
Security-Focused Workflow:
All Toolsets:
Documentation Updates
Files Created/Updated
.github/instructions/github-mcp-server.instructions.md.github/aw/github-agentic-workflows.md[context, repos, issues, pull_requests]to[context, repos, issues, pull_requests, actions, discussions, search]/tmp/gh-aw/cache-memory/github-mcp-tools.jsonAction Items
For Maintainers
list_labeltolist_labelsfor naming consistency (non-breaking change if aliased)For Users
actions,discussions, andsearchtoolsets.github/instructions/github-mcp-server.instructions.mdfor detailed tool informationConclusion
The GitHub MCP Remote Server provides a comprehensive, well-organized set of 56 tools across 19 toolsets. The JSON mapping is 100% accurate, and the toolset organization is logical with only minor naming inconsistencies. The recommended default toolsets have been updated to better serve common workflow patterns while maintaining security through explicit opt-in for sensitive operations.
Next Steps:
.github/instructions/github-mcp-server.instructions.mdReferences:
Beta Was this translation helpful? Give feedback.
All reactions