- Home
- MCP servers
- ChatGPT
ChatGPT
- typescript
15
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"toowiredd-chatgpt-mcp-server": {
"command": "docker",
"args": [
"run",
"-d",
"-p",
"3001:3001",
"--env-file",
".env",
"-v",
"/var/run/docker.sock:/var/run/docker.sock",
"chatgpt-mcp-server"
],
"env": {
"API_KEY": "YOUR_API_KEY_PLACEHOLDER",
"HTTP_PORT": "3001",
"RATE_LIMIT_WINDOW": "60000",
"RATE_LIMIT_REQUESTS": "100"
}
}
}
}You run a Model Context Protocol (MCP) server that lets you manage Docker containers through natural language. It handles resource management, rate limiting, and secure access so you can operate containers from an MCP client with confidence and reliability.
How to use
You connect an MCP client to the server and begin giving natural-language commands to manage Docker containers. Typical actions include listing running containers, starting or stopping containers, inspecting container details, and handling port mappings. The server enforces API key authentication, rate limiting, and graceful shutdown so you can integrate container operations into your workflows without worrying about resource leaks or unexpected downtime.
How to install
Prerequisites you need before installing: Node.js and npm are installed on your system. You will also use Docker to run the server container.
# Install via package manager (example for local setup)
npm install
# Build the TypeScript project (if you are building locally)
npm run build
# Run the server via Docker (example container run)
docker run -d \
-p 3001:3001 \
--env-file .env \
-v /var/run/docker.sock:/var/run/docker.sock \
chatgpt-mcp-server
Additional sections
Environment variables you configure to run the MCP server include API_KEY for authentication, HTTP_PORT to set the listening port, and rate limiting controls. You should provide these in an environment file or your preferred runtime environment.
Resource management is built in to gracefully handle shutdowns, track active connections, and release ports cleanly. If the server receives a shutdown signal, it stops accepting new connections, allows in-flight requests to finish, closes keep-alive connections, and frees all resources.
If you need to customize behavior, you can adjust the following environment variables in your .env file: API_KEY, HTTP_PORT, RATE_LIMIT_REQUESTS, RATE_LIMIT_WINDOW.
Available tools
docker_mcp
Expose MCP-driven container management capabilities to the client, enabling you to start, stop, inspect, and configure Docker containers through natural-language commands.
graceful_shutdown
Handle shutdown signals gracefully, flush in-flight requests, and release resources without errors.