mcp-gateway

Manage MCP Gateway lifecycle for GitHub MCP servers via Docker.

Updated Jan 14, 2026

Search Tags:#debugging #mcp #docker #containers #copilot #gateway #awf

Ready to run

npx skills add https://github.com/Mossaka/skills --skill mcp-gateway-mossaka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-gateway
Source: https://github.com/Mossaka/skills/tree/main/mcp-gateway
Command: npx skills add https://github.com/Mossaka/skills --skill mcp-gateway-mossaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The MCP Gateway management workflow simplifies launching, configuring, and debugging the MCP Gateway to run multiple MCP servers, reducing manual orchestration and error-prone setup.

Core Features & Use Cases

Lifecycle orchestration: start/stop gateway containers and spawn MCP server containers.
Health checks and debugging: verify gateway health, inspect logs, and troubleshoot token passthrough and authentication issues.
Copilot integration: configure Copilot to route prompts through the gateway, including AWF network setups.

Quick Start

Start the gateway and confirm it's healthy via the health endpoint.

Frequently Asked Questions about mcp-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate starting and stopping MCP Gateway containers?▼

You can automate MCP Gateway lifecycle management by using scripts that orchestrate starting, stopping, and spawning MCP server containers. This relies on Docker socket access to manage the gateway containers and deliver gateway configuration via stdin.

What is the best way to debug MCP Gateway health and authentication issues?▼

The best way to debug MCP Gateway issues is to run health checks against the gateway endpoint and inspect logs. This helps verify gateway health and troubleshoot token passthrough and authentication configuration problems.

How do I configure Copilot to route prompts through the MCP Gateway?▼

To configure Copilot integration, you route prompts through the MCP Gateway by applying the gateway configuration. This setup supports AWF network configurations and requires v0.0.59+ compatibility delivered via stdin.

Do I need Docker socket access to run an MCP Gateway server?▼

Yes, Docker socket access is required to run an MCP Gateway server. The gateway relies on Docker socket access to spawn MCP server containers and manage the lifecycle of the gateway orchestration.

How does the MCP Gateway handle configuration for v0.0.59+ compatibility?▼

For v0.0.59+ compatibility, the MCP Gateway handles configuration by receiving it directly via stdin. This stdin delivery method ensures the gateway can properly configure and manage multiple MCP servers.

Can I verify MCP Gateway health immediately after starting the container?▼

Yes, you can verify MCP Gateway health immediately after starting the container. The gateway provides a health endpoint that confirms the server is running correctly and ready to route Copilot prompts.