Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit41090e5

Browse files
authored
Update docs regarding MCP Server behaviour when bad toolsets are provided (#1398)
* update docs* update
1 parentb466148 commit41090e5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎docs/remote-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The Remote GitHub MCP server has optional headers equivalent to the Local server
5757

5858
-`X-MCP-Toolsets`: Comma-separated list of toolsets to enable. E.g. "repos,issues".
5959
- Equivalent to`GITHUB_TOOLSETS` env var for Local server.
60-
- If the list is empty, default toolsets will be used.If a bad toolset is provided, the server will fail to startandemit a 400 bad request status. Whitespace is ignored.
60+
- If the list is empty, default toolsets will be used.Invalid or unknown toolsets are silently ignored without errorandwill not prevent the server from starting. Whitespace is ignored.
6161
-`X-MCP-Readonly`: Enables only "read" tools.
6262
- Equivalent to`GITHUB_READ_ONLY` env var for Local server.
6363
- If this header is empty, "false", "f", "no", "n", "0", or "off" (ignoring whitespace and case), it will be interpreted as false. All other values are interpreted as true.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp