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-12Lines changed: 5 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ If you don't have Docker, you can use `go build` to build the binary in the
112
112
113
113
## Tool Configuration
114
114
115
-
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.
115
+
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.
116
116
117
117
### Available Toolsets
118
118
@@ -129,7 +129,7 @@ The following sets of tools are available (all are on by default):
129
129
130
130
#### Specifying Toolsets
131
131
132
-
To reduce the available tools, you can pass an allow-list in two ways:
132
+
To specify toolsets you want available to the LLM, you can pass an allow-list in two ways:
133
133
134
134
1.**Using Command Line Argument**:
135
135
@@ -144,11 +144,6 @@ To reduce the available tools, you can pass an allow-list in two ways:
144
144
145
145
The environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided.
146
146
147
-
Any toolsets you specify will be enabled from the start, including when `--dynamic-toolsets` is on.
148
-
149
-
You might want to do this if the model is confused about which tools to call and you only require a subset.
150
-
151
-
152
147
### Using Toolsets With Docker
153
148
154
149
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.
180
-
This feature provides tools that help the MCP Host application to discover and enable sets of GitHub tools only when needed.
181
-
This helps to avoid situations where models get confused by the shear number of tools available to them, which varies by model.
174
+
**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.
175
+
176
+
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.
182
177
183
178
### Using Dynamic Tool Discovery
184
179
@@ -197,8 +192,6 @@ docker run -i --rm \
197
192
ghcr.io/github/github-mcp-server
198
193
```
199
194
200
-
201
-
202
195
## GitHub Enterprise Server
203
196
204
197
The flag `--gh-host` and the environment variable `GH_HOST` can be used to set
0 commit comments