Container Exec MCP Server
Enables AI assistants to manage Docker containers, execute commands inside them, and inspect container information through a minimalist set of tools supporting both stdio and HTTP transports.
README
Container Exec MCP Server

A Model Context Protocol (MCP) server that provides Docker container automation capabilities. This server enables AI assistants like Claude/Cursor/ChatGPT to manage and interact with Docker containers, execute commands, and inspect container information.
This package minimizes the amount of tools to help AI Agents pick the right tool for a given prompt.
Features
- 🐳 Container Management - List and inspect Docker containers
- 🔧 Command Execution - Execute commands inside containers
- 📊 Detailed Information - Get comprehensive container details
- 🚀 Dual Transport - HTTP and stdio (for Claude Code/Cursor)
For detailed information about available tools, see tools.md.
Table of Contents
- Container Exec MCP Server
Getting Started
Prerequisites
- Node.js 18 or higher
- Docker installed and running
- npm or yarn
Configuration
Environment Variables
Configure the server behavior using environment variables:
| Variable | Description | Default | Options |
|---|---|---|---|
PORT |
HTTP server port | 4200 |
Any valid port number |
MCP_AUTH_TOKEN |
Authentication token for HTTP server (optional) | None | Any string |
Cursor / Claude Code / Claude Desktop Configuration
To use this server with Cursor/Claude Code/Claude Desktop, add it to your MCP settings file.
Configuration:
{
"mcpServers": {
"container-exec": {
"command": "npx",
"args": [
"container-exec-mcp"
]
}
}
}
Note: After updating the configuration, restart Claude Code/Desktop for changes to take effect.
Important: Ensure Docker is running and accessible on your system.
HTTP Transport (for n8n or other HTTP clients)
Start the HTTP server:
npm install
npm start
# or with custom port
PORT=4200 npm start
# With authentication (recommended)
MCP_AUTH_TOKEN=your-secret-token npm start
The server will listen on http://localhost:4200/mcp (or your custom port).
Authentication (Optional):
You can secure the HTTP server with token-based authentication by setting the MCP_AUTH_TOKEN environment variable. If set, all requests must include the token in the Authorization header.
Example HTTP Request (with authentication):
curl -X POST http://localhost:4200/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer your-secret-token" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_containers",
"arguments": {
"all": true
}
}
}'
Development
Development Scripts
npm install
# Start HTTP server with auto-reload
npm run dev
# Start stdio server with auto-reload
npm run dev:stdio
# Build TypeScript to JavaScript
npm run build
Troubleshooting
Common Issues
1. Docker not running
Error: connect ENOENT /var/run/docker.sock
Solution: Start Docker Desktop or the Docker daemon.
2. Docker permission denied
Error: permission denied while trying to connect to the Docker daemon socket
Solution: On Linux, add your user to the docker group: sudo usermod -aG docker $USER (then log out and back in).
3. Node.js version too old
Error: Node.js 18 or higher required
Solution: Update Node.js to version 18 or higher.
4. Container not found
Error: No such container: xyz
Solution: Verify the container ID or name with list_containers.
5. Port already in use (HTTP mode)
Error: listen EADDRINUSE: address already in use :::4200
Solution: Change the port with PORT=3001 npm start
Debug Logging
For stdio mode, logs are written to stderr and appear in Claude Code logs:
- macOS:
~/Library/Logs/Claude/mcp-server-container-exec-mcp.log - Linux:
~/.config/Claude/logs/mcp-server-container-exec-mcp.log
For HTTP mode, logs appear in the terminal where you started the server.
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Run
npm run buildto ensure it compiles - Test your changes
- Submit a pull request
License
MIT
Acknowledgments
Built with:
- Dockerode - Docker API client
- Model Context Protocol SDK - MCP implementation
- Zod - Schema validation
- Express - HTTP server
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.