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
You can configure toolsets and readonly mode by providing HTTP headers in yourserverconfiguration.
50
+
The Remote GitHub MCP server has optional headers equivalent to the Localserverenv vars:
51
51
52
-
The headers are:
53
-
-`X-MCP-Toolsets=<toolset>,<toolset>...`
54
-
-`X-MCP-Readonly=true`
52
+
-`X-MCP-Toolsets`: Comma-separated list of toolsets to enable. E.g. "repos,issues".
53
+
- Equivalent to`GITHUB_TOOLSETS` env var for Local server.
54
+
- If the list is empty, default toolsets will be used. If a bad toolset is provided, the server will fail to start and emit a 400 bad request status. Whitespace is ignored.
55
+
-`X-MCP-Readonly`: Enables only "read" tools.
56
+
- Equivalent to`GITHUB_READ_ONLY` env var for Local server.
57
+
- 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.
58
+
59
+
Example:
60
+
61
+
```json
62
+
{
63
+
"type":"http",
64
+
"url":"https://api.githubcopilot.com/mcp/",
65
+
"headers": {
66
+
"X-MCP-Toolsets":"repos,issues",
67
+
"X-MCP-Readonly":"true"
68
+
}
69
+
}
70
+
```
71
+
72
+
###URL Path Parameters
73
+
74
+
The Remote GitHub MCP server also supports the URL path parameters:
75
+
76
+
-`/x/{toolset}`
77
+
-`/x/{toolset}/readonly`
78
+
-`/readonly`
79
+
80
+
Note:`{toolset}` can only been a single toolset, not a comma-separated list. To combine multiple toolsets, use the`X-MCP-Toolsets` header instead.