🧭 Epic

Title: Publish multi-architecture ARM64 Docker image for MCP Gateway
Goal: Enable seamless deployment of MCP Gateway on ARM64 platforms such as Apple Silicon Macs by providing an official ARM64 or multi-architecture Docker image.
Why now: The current official image only supports amd64 architecture, causing compatibility issues on ARM64 systems. Publishing a multi-arch image benefits developers and users running MCP Gateway on diverse hardware, improving adoption and ease of use.

🧭 Type of Feature

• Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)

🙋‍♂️ User Story 1

As a: Developer or DevOps engineer
I want: The MCP Gateway Docker image to support ARM64 architecture
So that: I can deploy and test MCP Gateway natively on ARM64 platforms without building images locally or using emulation

✅ Acceptance Criteria

Scenario: Pulling the MCP Gateway image on ARM64 platform
  Given I am running on an ARM64 machine
  When I pull the official MCP Gateway Docker image
  Then the image should run natively without architecture compatibility errors

Scenario: CI/CD pipeline builds and publishes multi-arch images
  Given the MCP Gateway source code repository
  When a new release is built
  Then the CI/CD pipeline publishes images for amd64 and arm64 architectures

🙋‍♂️ User Story 2

As a: User of MCP Gateway on ARM64 hardware
I want: Clear documentation and examples on how to use the multi-arch image
So that: I can easily deploy MCP Gateway without manual image building or workarounds

✅ Acceptance Criteria

Scenario: Documentation includes multi-arch image usage
  Given the MCP Gateway documentation
  When I read the deployment instructions
  Then I see guidance on pulling and using the multi-arch image on ARM64 platforms

📐 Design Sketch (optional)

Include a diagram, sketch, or flow (use Mermaid if desired):

flowchart TD
    A[CI/CD Pipeline] -->|Build multi-arch images| B(Docker Buildx)
    B --> C[Push to GitHub Container Registry]
    C --> D[Users pull multi-arch image]
    D --> E[Run MCP Gateway on amd64 or arm64]

🔗 MCP Standards Check

• Change adheres to current MCP specifications
• No breaking changes to existing MCP-compliant integrations

🔄 Alternatives Considered

• Manual local image builds for ARM64 (less convenient)
• Using emulation (slower, less reliable)
• Publishing separate ARM64 and amd64 images (more complex to manage)

📓 Additional Context

• This feature complements the Helm chart for MCP Gateway by ensuring the container image is compatible with all target platforms.
• Related to ongoing efforts to improve developer experience and deployment automation.
• May require updates to CI/CD workflows and documentation.