Skip to content

Add container images workflow for multi-arch container builds - #4634

Closed
creydr wants to merge 1 commit into
modelcontextprotocol:mainfrom
creydr:add-container-images-workflow
Closed

creydr wants to merge 1 commit into
modelcontextprotocol:mainfrom
creydr:add-container-images-workflow

Conversation

@creydr

@creydr creydr commented Aug 12, 2026

Copy link
Copy Markdown

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 and latest).
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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation (n/a)
  • My changes follows MCP security best practices (n/a)
  • I have updated the server's README accordingly
  • I have tested this with an LLM client (n/a)
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling (n/a)
  • I have documented all environment variables and configuration options (n/a)

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.
@creydr creydr changed the title Add container images workflow for multi-arch Docker builds Add container images workflow for multi-arch container builds Aug 12, 2026
@creydr

creydr commented Aug 13, 2026

Copy link
Copy Markdown
Author

@olaservo @domdomegg could I get a review on this when you have a chance?

@creydr

creydr commented Aug 29, 2026

Copy link
Copy Markdown
Author

@olaservo @domdomegg could you check on this?

@creydr

creydr commented Sep 9, 2026

Copy link
Copy Markdown
Author

@olaservo @domdomegg could you check on this or ping somebody who could review it?

@cliffhall cliffhall added the closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875) label Oct 20, 2026
@cliffhall

Copy link
Copy Markdown
Member

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 CONTRIBUTING.md.

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.

@cliffhall cliffhall closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants