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
+51Lines changed: 51 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -345,6 +345,38 @@ To specify toolsets you want available to the LLM, you can pass an allow-list in
345
345
346
346
The environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided.
347
347
348
+
#### Specifying Individual Tools
349
+
350
+
You can also configure specific tools using the `--tools` flag. Tools can be used independently or combined with toolsets and dynamic toolsets discovery for fine-grained control.
This registers `get_file_contents` plus the dynamic toolset tools (`enable_toolset`, `list_available_toolsets`, `get_toolset_tools`).
374
+
375
+
**Important Notes:**
376
+
- Tools, toolsets, and dynamic toolsets can all be used together
377
+
- Read-only mode takes priority: write tools are skipped if `--read-only` is set, even if explicitly requested via `--tools`
378
+
- Tool names must match exactly (e.g., `get_file_contents`, not `getFileContents`). Invalid tool names will cause the server to fail at startup with an error message
379
+
348
380
### Using Toolsets With Docker
349
381
350
382
When using Docker, you can pass the toolsets as environment variables:
@@ -356,6 +388,25 @@ docker run -i --rm \
356
388
ghcr.io/github/github-mcp-server
357
389
```
358
390
391
+
### Using Tools With Docker
392
+
393
+
When using Docker, you can pass specific tools as environment variables. You can also combine tools with toolsets:
0 commit comments