fix: use ENTRYPOINT and CMD for proper argument handling

[JAORMX]

Problem

The current Dockerfile uses CMD ["./github-mcp-server", "stdio"] which causes issues when container orchestration tools try to append additional arguments. This results in the entire CMD being replaced rather than arguments being appended.

Root Cause

When using only CMD, container runtimes replace the entire command when additional arguments are provided. This breaks argument passing in tools like ToolHive, Kubernetes, and other container orchestrators.

Solution

Implement Docker best practices by using:

• ENTRYPOINT for the executable that should always run
• CMD for default arguments that can be overridden/appended to

Changes

Before:

CMD ["./github-mcp-server", "stdio"]

After:

ENTRYPOINT ["./github-mcp-server"]
CMD ["stdio"]

Benefits

1. Proper argument handling: Additional arguments are appended to the default stdio argument instead of replacing the entire command
2. Container orchestration compatibility: Works correctly with Kubernetes, Docker Compose, and other tools
3. Backward compatibility: Default behavior remains the same when no arguments are provided
4. Docker best practices: Follows recommended patterns for containerized applications

Testing

This change maintains backward compatibility:

• docker run github-mcp-server → runs ./github-mcp-server stdio (same as before)
• docker run github-mcp-server --toolsets all → runs ./github-mcp-server --toolsets all (new capability)

Related Issues

This fixes argument passing issues reported in container orchestration tools where additional arguments couldn't be properly passed to the MCP server.

[Copilot]

Pull Request Overview

Switch from a single CMD to using ENTRYPOINT plus a default CMD in the Dockerfile to enable proper argument appending.

• Introduce ENTRYPOINT for the server binary
• Keep default stdio argument in CMD
• Update comments to reflect the change

[SamMorrowDrums]

This is great, would you mind updating the README.me so that any suggested commands are correct for this change?

[JAORMX]

@SamMorrowDrums can you explain a little more? I'm not sure anything would need to change from the README

[SamMorrowDrums]

I haven't double checked, if we don't suggest anything that would need to change that's no problem.

[JAORMX]

@SamMorrowDrums right! the idea is that nothing changes. But this enables for orchestration platforms to actually be able to pass parameters in an easier way. This wasn't part of the README before, so there was nothing to change.

[SamMorrowDrums]

The kind of things I was think were additional arguments in the docs like --export-translations which would change from be ./github-mcp-server stdio --export-translations to stdio --export-translations if I understand correctly?

Maybe we don't explicitly spell any of them out. I've definitely provided such commands via issues, but that's all I wanted to ensure. I think fortunately the docs are lacking enough that you don't have anything to update.

[JAORMX]

@SamMorrowDrums I can check out the README to add/modify examples. Mind if I do that in a separate PR?

[JAORMX]

@SamMorrowDrums for now, without this fix, we can't pass command line arguments to the GitHub MCP server with ToolHive and Kubernetes.