Docker Mcp Server

Docker MCP Server

A Model Context Protocol (MCP) server that runs entirely inside a Docker container, providing secure command execution and file operations through HTTP with bearer token authentication.

🚀 Features

• Containerized MCP Server: Runs entirely inside Docker with no host dependencies
• HTTP Transport: Network-based communication with bearer token authentication
• Secure Command Execution: Run shell commands in isolated container environment
• File Operations: Read, write, edit, and search files within container workspace
• Process Management: Track long-running processes with unique IDs
• Interactive Input: Send input to running processes
• Smart Timeouts: Intelligent process timeout handling based on output activity

🏗️ Architecture

The MCP server runs inside a Docker container and communicates with clients over HTTP:

MCP Client (via HTTP) ↔ Docker Container (Port 3000)
                              ↓
                        MCP Server (Node.js)
                              ↓
                    Workspace (/app/workspace)
                              ↓
                    Host ./tmp directory (mounted)

Core Components

• Containerized MCP Server - TypeScript server using @modelcontextprotocol/sdk with StreamableHTTPServerTransport
• HTTP API - Network-based communication on port 3000
• Bearer Token Auth - Secure authentication for all requests
• Docker Container - Debian-based with Node.js, Playwright, and development tools
• Workspace Mount - Host ./tmp directory mounted to /app/workspace
• Process Tracking - Background process management with unique IDs

Key Differences from Traditional MCP Servers

• No Host Installation: Server runs entirely in container
• Network Access: HTTP-based instead of stdio transport
• Authentication Required: Bearer token for all requests
• Self-Contained: All dependencies bundled in container image
• **Direct Exec