[Feature Request]: Air-Gapped Environment Support

[AmshegaR]

🧭 Type of Feature

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

🧭 Epic

Title: Air-Gapped Environment Support for MCP Context Forge

Goal:
Enable MCP Context Forge Gateway to run fully offline in secure, air-gapped environments without external CDN dependencies.

Why now:
Many enterprise and government organizations require air-gapped deployments for security compliance. Currently, the admin UI and Swagger fail to function properly due to CDN dependencies and initialization timing issues in offline environments.

Proposed Solution:
When the AIR_GAPPED environment variable is set:

• All required static assets (e.g., Tailwind, CodeMirror, Chart.js, Alpine.js, swagger-ui.css, etc.) should be bundled locally into a /static folder.
• The application should serve these assets directly, avoiding any dependency on external CDNs.
• Ensure Swagger UI and Admin UI initialize reliably in offline mode.

Impact:

• Expands compatibility with enterprise and government users.
• Improves deployment flexibility in restricted network environments.
• Reduces risk of UI breakages caused by CDN outages or network restrictions.