You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-12
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ If you don't have Docker, you can use `go build` to build the binary in the
110
110
111
111
## Tool Configuration
112
112
113
-
The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the `--toolsets` flag. This allows you to control which GitHub API capabilities are available to your AI tools.
113
+
The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the `--toolsets` flag. This allows you to control which GitHub API capabilities are available to your AI tools. Enabling only the toolsets that you need can help the LLM with tool choice and reduce the context size.
114
114
115
115
### Available Toolsets
116
116
@@ -127,7 +127,7 @@ The following sets of tools are available (all are on by default):
127
127
128
128
#### Specifying Toolsets
129
129
130
-
To reduce the available tools, you can pass an allow-list in two ways:
130
+
To specify toolsets you want available to the LLM, you can pass an allow-list in two ways:
131
131
132
132
1.**Using Command Line Argument**:
133
133
@@ -142,11 +142,6 @@ To reduce the available tools, you can pass an allow-list in two ways:
142
142
143
143
The environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided.
144
144
145
-
Any toolsets you specify will be enabled from the start, including when `--dynamic-toolsets` is on.
146
-
147
-
You might want to do this if the model is confused about which tools to call and you only require a subset.
148
-
149
-
150
145
### Using Toolsets With Docker
151
146
152
147
When using Docker, you can pass the toolsets as environment variables:
Instead of starting with all tools enabled, you can turn on Dynamic Toolset Discovery.
178
-
This feature provides tools that help the MCP Host application to discover and enable sets of GitHub tools only when needed.
179
-
This helps to avoid situations where models get confused by the shear number of tools available to them, which varies by model.
172
+
**Note**: This feature is currently in beta and may not be available in all environments. Please test it out and let us know if you encounter any issues.
173
+
174
+
Instead of starting with all tools enabled, you can turn on dynamic toolset discovery. Dynamic toolsets allow the MCP host to list and enable toolsets in response to a user prompt. This should help to avoid situations where the model gets confused by the shear number of tools available.
180
175
181
176
### Using Dynamic Tool Discovery
182
177
@@ -195,8 +190,6 @@ docker run -i --rm \
195
190
ghcr.io/github/github-mcp-server
196
191
```
197
192
198
-
199
-
200
193
## GitHub Enterprise Server
201
194
202
195
The flag `--gh-host` and the environment variable `GH_HOST` can be used to set
0 commit comments