Adding default toolset grouping #1159
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new "stargazers" toolset grouping by moving stargazer-related tools from the repositories toolset into their own dedicated group, and updates the default tools list to include specific toolsets instead of "all".
- Moved stargazer tools (list_starred_repositories, star_repository, unstar_repository) from repositories to a new dedicated stargazers toolset
- Updated DefaultTools to explicitly list toolsets: "context", "repos", "issues", "pull_requests", "users" instead of using "all"
- Added documentation entries for the new stargazers toolset in both remote server documentation and README
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pkg/github/tools.go | Creates new stargazers toolset and moves stargazer tools from repositories toolset, updates DefaultTools list |
| docs/remote-server.md | Adds stargazers toolset entry to the remote server toolsets table |
| README.md | Moves stargazer tool documentation from repositories section to new stargazers section and updates toolsets list |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
IrynaKulakova
approved these changes
Oct 1, 2025
almaleksia
reviewed
Oct 1, 2025
| } | ||
| ToolsetMetadataDynamic = ToolsetMetadata{ | ||
| ID: "dynamic", | ||
| Description: "Discover GitHub MCP tools that can help achieve tasks by enabling additional sets of tools, you can control the enablement of any toolset to access its tools when this toolset is enabled.", |
Contributor
There was a problem hiding this comment.
shall we include this in the default? This would allow agent to see what tools are available and prompt to enable them.
Contributor
Author
There was a problem hiding this comment.
Hmm right now its turned off i need to test it a bit better to make a judgement
almaleksia
approved these changes
Oct 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a data-driven default toolset configuration to improve performance, reduce inference costs, and provide a better out-of-the-box experience for GitHub MCP Server users.
Problem
The current "all tools enabled by default" approach causes several issues:
Changes
New Default Toolsets (Data-Driven Selection)
Based on real-world usage analysis across all sessions, the new default includes the 5 most-used toolset groups:
context- Current user and GitHub contextrepos- Repository operationsissues- Issue trackingpull_requests- PR workflowsusers- User informationThese cover almost all top 20 most frequently used tools.
Code Changes
pkg/github/tools.go:ToolsetMetadatastruct to hold toolset ID and descriptionGetDefaultToolsetIDs()to return curated default listGenerateToolsetsHelp()for improved CLI help textreposto new dedicatedstargazerstoolsetcmd/github-mcp-server/main.go:GetDefaultToolsetIDs()when no toolsets specifiedGenerateToolsetsHelp()README.md:stargazerstoolset to available toolsets tabledocs/remote-server.md:stargazerstoolset to remote server documentationPerformance Improvements compared to old default("all")
Token Reduction
User Experience Benefits
Future Work
repos,pull_requests) into more specialized subgroupsTesting
--toolsetsflag provided--toolsets allstill enables all toolsets