toolset does not exists using GITHUB_TOOLSETS

[raythurnvoid]

Describe the bug

I get 2025/04/18 01:55:24 Failed to initialize toolsets:toolset repos,issues,pull_requests,code_security does not exist

Affected version

GitHub MCP Server
Version: v0.2.0
Commit: 8991436
Build Date: 2025-04-17T13:39:10Z

Steps to reproduce the behavior

docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN="xxx" -e GITHUB_TOOLSETS="repos,issues,pull_requests,code_security" ghcr.io/github/github-mcp-server

[SamMorrowDrums]

Thank you for this report. Can you try the following

docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN="xxx" ghcr.io/github/github-mcp-server ./github-mcp-server stdio --toolsets repos,issues,pull_requests,code_security

I am wondering if the env var parsing is failing to split the CSV into by comma.

[raythurnvoid]

With --toolsets it works!

[SamMorrowDrums]

Ok this will be fixing for sure. Thank you.

[jpetrantoni]

@williammartin
This issue is still happening, the below space separate env is working properly

However the below config results in the error log of

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--toolsets": executable file not found in $PATH: unknown.
ERROR [2025-05-07 01:07:05.369 -0400] (LLM - MastraMCPClient): [github] McpError: MCP error -32000: Connection closed
    at Client._onclose (file:///Users/joepetrantoni/nest/node_modules/.pnpm/@modelcontextprotocol+sdk@1.10.2/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:97:23)
    at _transport.onclose (file:///Users/joepetrantoni/nest/node_modules/.pnpm/@modelcontextprotocol+sdk@1.10.2/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:69:18)
    at ChildProcess.<anonymous> (file:///Users/joepetrantoni/nest/node_modules/.pnpm/@modelcontextprotocol+sdk@1.10.2/node_modules/@modelcontextprotocol/sdk/dist/esm/client/stdio.js:85:77)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)

Passing the path and stdio arg fixes it still

[williammartin]

I don't think we've done a release since the PR was merged (one of the funny quirks of shipping a binary but using GitHub's Fixes notation on PRs).

[jpetrantoni]

No worries, more-so didnt know if it was an issue with my docker. Thanks for you reply