-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
A clear and concise description of what the bug is.
When I run:
docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN=<redacted> -e GITHUB_TOOLSETS="discussions" ghcr.io/github/github-mcp-server
I get:
failed to create MCP server: failed to enable toolsets: toolset discussions does not exist
Works fine with other toolsets I've tried.

Discussions also appear to be not working on the remote server --
VS Code config:
"mcp": {
"servers": {
"gh-discussions": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/x/discussions/readonly"
},
}
Output on startup:
2025-07-10 11:45:08.703 [info] Starting server from LocalProcess extension host
2025-07-10 11:45:08.703 [info] Connection state: Running
2025-07-10 11:45:09.775 [info] 400 status sending message to https://api.githubcopilot.com/mcp/x/discussions/readonly, will attempt to fall back to legacy SSE
2025-07-10 11:45:10.090 [info] Connection state: Error 400 status connecting to https://api.githubcopilot.com/mcp/x/discussions/readonly as SSE: failed to create MCP server, bad request: toolset discussions does not exist
I don't experience the same problem with e.g. https://api.githubcopilot.com/mcp/x/issues/readonly
.
Affected version
docker run -i --rm ghcr.io/github/github-mcp-server --version
GitHub MCP Server
Version: v0.6.0
Commit: 721fd3e3c8a745d4b6147749dc606a05ebf9dbfc
Build Date: 2025-07-01T13:22:28Z
Steps to reproduce the behavior
- Run
docker pull ghcr.io/github/github-mcp-server
- Run
docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN=<redacted> -e GITHUB_TOOLSETS="discussions" ghcr.io/github/github-mcp-server
with a valid PAT - See error
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working