Toowiredd Chatgpt MCP Server

🚀 ChatGPT Server Based on Model Context Protocol (MCP)

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, built on the Model Context Protocol (MCP).

✨ Features

• Manage Docker containers using natural language.
• Built on the Model Context Protocol (MCP).
• Implemented in TypeScript.
• Supports containerized deployment.
• Features robust error handling and graceful shutdown capabilities.
• Excels in resource management and port handling.
• Provides rate limiting and API key authentication.

📦 Installation

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 as needed.

4. Build the project.

npm run build

Run with Docker

1. Build the container image.

npm run docker:build

2. Start the container.

npm run docker:run

Or manually execute:

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

💻 Usage Examples

Development Commands

• npm run build: Build the TypeScript code.
• npm run watch: Watch for file changes and automatically rebuild.
• npm run inspector: Run the MCP inspector tool.

📚 Documentation

Environment Variables

Resource Management

This server has powerful resource management capabilities:

• Supports signal handling for graceful shutdown (supports SIGINT, SIGTERM, SIGQUIT).
• Terminates new connection requests after rejection.
• Allows active requests to complete with a timeout limit.
• Manages the survival status of active connections.
• Tracks and releases server port resources.
• Ensures all resources are released correctly.

Shutdown Process

1. When the server receives a shutdown signal, it starts the graceful shutdown logic.
2. Rejects new connection requests.
3. Allows existing requests to continue processing with a timeout.
4. Actively disconnects persistent connections.
5. Correctly releases occupied port resources.
6. Ensures all resources are properly handled.

Error Handling Mechanism

• Monitors port conflicts and reports them in a timely manner.
• Catches unhandled rejections and exceptions.
• Handles errors in network transmission.
• Prevents resource leaks and ensures correct release.
• Sets a timeout to avoid long - term server hangs.