Add Dockerfile and GHCR publishing for MCP server

[kvz]

Summary

• Adds packages/mcp-server/Dockerfile — lightweight image using node:22-alpine + npm install
• Adds .github/workflows/docker-mcp.yml — auto-publishes to ghcr.io/transloadit/mcp-server on release
• Includes patch changeset to trigger a release

Why

• Glama directory requires a Docker image for health checks (blocks punkpeye/awesome-mcp-servers PR #1912)
• Unlocks Docker MCP Catalog submission (github.com/docker/mcp-registry)
• Gives users a containerized self-hosting option

Verified locally

$ docker build -t test packages/mcp-server/
$ echo '{"jsonrpc":"2.0","id":1,"method":"initialize",...}' | docker run -i test
{"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{"listChanged":true}},"serverInfo":{"name":"Transloadit MCP","version":"0.3.7"}},"jsonrpc":"2.0","id":1}

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 26b1df34ee

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Pin npm package version in Docker image build

The image always installs @transloadit/mcp-server@latest, so the binary inside the container is not tied to the GitHub release tag being published. If latest differs from the release version (for example, rerunning an older release workflow or any dist-tag drift), ghcr.io/transloadit/mcp-server:<release-version> will contain the wrong server code, which breaks version correctness and reproducibility for users pulling pinned image tags.

Useful? React with 👍 / 👎.