Summary

Add an MCP Client service to the docker-compose configuration, such as MCP Inspector, pre-configured to connect to a virtual server.

Motivation

Having an MCP client bundled in the docker-compose setup would:

• Provide immediate visibility into registered MCP servers and their capabilities
• Enable quick testing and debugging of tool calls without external tooling
• Lower the barrier to entry for new users exploring the gateway
• Serve as a reference implementation for client configuration

Proposed Solution

1. Add MCP Inspector (or similar client) as a service in docker-compose.yml
2. Pre-configure it to connect to the gateway's SSE/WebSocket endpoint
3. Set up appropriate environment variables for authentication
4. Document the setup in the README

Example Configuration

services:
  mcp-inspector:
    image: mcp/inspector:latest  # or appropriate image
    ports:
      - "5173:5173"
    environment:
      - MCP_SERVER_URL=http://mcpgateway:4444/servers/{server_id}/sse
      - AUTH_TOKEN=${MCPGATEWAY_BEARER_TOKEN}
    depends_on:
      - mcpgateway

Acceptance Criteria

• MCP Inspector (or equivalent) added to docker-compose
• Client auto-connects to a demo virtual server
• Authentication pre-configured using existing env vars
• Documentation updated with usage instructions