Repository navigation
Conversation
Builds and pushes multi-arch (amd64/arm64) container images to GHCR for all servers under src/ that have a Dockerfile. Triggers on push to main (tagged "main") and on release (tagged with release version and "latest"). Uses dynamic server detection to avoid a static build matrix.
|
@olaservo @domdomegg could I get a review on this when you have a chance? |
|
@olaservo @domdomegg could you check on this? |
|
@olaservo @domdomegg could you check on this or ping somebody who could review it? |
|
Thank you for this pull request, and apologies for the long wait for a response. These servers are reference implementations: they exist to show how each part of MCP is used, not to be general-purpose products, so new features are taken selectively, and this change isn't one the maintainers plan to take. This repository also now accepts issues, not pull requests, from anyone but its maintainers; the policy is in This is not a judgment on the idea or on you. A server in the MCP Registry may well offer it, and anyone is welcome to build on these servers to do so. If you think we've misread it, please open an issue describing the problem and the expected behavior. This is part of the backlog triage in #4875. |
Provide container images of servers.
Description
Currently the servers are not provided as container images. This PR addresses it and builds and pushes multi-arch (amd64/arm64) container images to GHCR for all servers under
src/that have a Dockerfile.Triggers on push to main (tagged
main) and on release (tagged with release version andlatest).Uses dynamic server detection to avoid a static build matrix.
Publishing Your Server
n/a
Server Details
n/a
Motivation and Context
To run the MCP Servers for example on Kubernetes, we need those as a container image. As the servers already have the Dockerfiles, there is no need for the users to build them on their own each time, when we could provide them here centrally.
How Has This Been Tested?
n/a
Breaking Changes
no
Types of changes
Checklist