Docker Manager

🚀 ChatGPT MCP Server

A Model Context Protocol (MCP) server that provides Docker management capabilities through a custom GPT interface.

🚀 Quick Start

This server offers Docker management features via a custom GPT interface, enabling users to manage Docker containers using natural language.

✨ Features

• Manage Docker containers using natural language.
• Based on the Model Context Protocol (MCP).
• Implemented in TypeScript.
• Containerized deployment.
• Robust error handling and graceful shutdown.
• Resource management and port handling.
• Rate limiting and API key authentication.

📦 Installation

Install via Smithery

To automatically install the ChatGPT MCP Server for Claude Desktop via Smithery:

npx -y @smithery/cli install @Toowiredd/chatgpt-mcp-server --client claude

Manual Installation

1. Clone the repository

git clone https://github.com/toowiredd/chatgpt-mcp-server.git
cd chatgpt-mcp-server

2. Install dependencies

npm install

3. Create an environment file

cp env.example .env
# Edit the .env file to configure your settings

4. Build the project

npm run build

Running with Docker

1. Build the container

npm run docker:build

2. Run the container

npm run docker:run

Or run it manually:

docker run -d \
  -p 3001:3001 \
  --env-file .env \
  -v /var/run/docker.sock:/var/run/docker.sock \
  chatgpt-mcp-server

💻 Usage Examples

Development

• npm run build - Build the TypeScript code.
• npm run watch - Monitor changes and automatically rebuild.
• npm run inspector - Run the MCP inspection tool.

📚 Documentation

Environment Variables

Resource Management

This server implements robust resource management:

• Perform graceful shutdown on process signals (SIGINT, SIGTERM, SIGQUIT).
• Reject new connections.
• Allow active requests to complete (with a timeout).
• Close keep-alive connections.
• Properly release the server port.
• Correctly release resources through appropriate handling.

Shutdown Process

1. The server initiates a graceful shutdown on process signals.
2. New connections are rejected.
3. Active requests are allowed to complete (with a timeout).
4. Keep-alive connections are closed.
5. The server port is properly released.
6. Resources are correctly released through appropriate handling.

Error Handling

• Detect and report port conflicts.
• Catch unhandled rejections and exceptions.
• Properly handle network errors.
• Prevent resource leaks through appropriate handling.
• Ensure the server does not hang during shutdown through timeouts.

📄 License

MIT