eg

The EGMCP Server acts as an MCP gateway between Claude Desktop and your Envoy Gateway installation. It exposes 11 specialized tools that let you read configuration and state in real-time, while also providing controlled write operations and advanced traffic management capabilities. You can query listeners, routes, and clusters, monitor health and status, and perform route creation, deletion, and listener management. The server supports features like dry-run mode for manifest generation and a read-only mode to ensure safe monitoring in production environments. With Kubernetes integration and multi-environment support, you can manage production, staging, and development configurations from a single toolset.

To use the tools, install the MCP server (via NPX for zero-install convenience) and point Claude Desktop to the mcpServers entry. The standard workflow runs the stdio-tools command against Envoy Gateway, returning structured results and enabling natural-language guided operations such as creating routes, adjusting traffic splitting, or applying load-balancing policies. For write operations, consider enabling dry-run or read-only options to validate changes before applying them in your environment.

Option B: Binary installation (server-side in environments with curl access)\n1. Ensure prerequisites are met (Node.js not required for binary-based install in this approach if a binary is provided by the repository).\n2. Run the install script from the project to fetch and install the MCP server binary:\nbash\ncurl -sSL https://raw.githubusercontent.com/saptak/eg-mcp-server/main/install.sh | bash\n\n3. After installation, verify the binary is in your PATH and accessible:\nbash\negmcp-server --version\n\n4. Start the server with appropriate flags for your environment (example used in NPX setup).

Tips and common considerations:\n- Ensure the Envoy Gateway admin API is reachable from the MCP server host. Network policies or firewalls may block access to http://localhost:19001.\n- Use the read-only mode for production monitoring to avoid unintended changes.\n- For write operations, consider using the dry-run mode first to generate YAML manifests before applying changes.\n- When configuring Claude Desktop, align the mcpServers entry name with your UI configuration and ensure the command/args reflect your installation method.\n- If your environment uses Kubernetes, provide the kubeconfig path via the mcpServers args to enable resource CRUD operations.\n- The mcpServers configuration can be extended to multiple servers or environments by duplicating entries under mcpServers.\n- Monitor logs for authentication/permission errors and ensure RBAC policies permit the MCP server to read and write Envoy Gateway resources as needed.