Docker is a software platform that allows you to build, test, and deploy applications quickly using containers. Containers let developers package up an application with all of the parts it needs, such as libraries and other dependencies, and ship it all out as one package.
Why this server?
Supports deployment as a Docker container with pre-built images available from GitHub Container Registry
Why this server?
Supports running the MCP server in a Docker container, with the ability to mount local Pulumi project directories to perform operations on containerized Pulumi projects.
Why this server?
Supports running the MCP server in a Docker container for a secure, sandboxed environment with minimal blast radius.
Why this server?
Provides instructions for running the MCP server in a containerized environment using Docker.
Why this server?
Enables running the Optuna MCP server in a containerized environment with volume mounting for persistence of optimization results.
Why this server?
Supports containerized deployment using Docker with cross-platform compatibility and isolated environment.
Why this server?
Supports containerized deployment through Docker, enabling portable and isolated execution of the Twelve Data MCP server
Why this server?
Supports containerized deployment of the MCP server with detailed Dockerfile configuration
Why this server?
Provides Docker container deployment option for running the MCP server with configurable environment variables
Why this server?
Provides tools for monitoring running Docker container images across runtime clusters with their security and operational status through JFrog's runtime services.
Why this server?
Provides a containerized deployment option for running the CoinStats MCP server in a Docker environment, allowing for isolated and portable execution.
Why this server?
Enables running Memgraph MAGE in a Docker container with schema information enabled, making the database accessible for LLM interactions
Why this server?
Can be deployed as a Docker container, making the WeatherXM PRO API available through the MCP protocol
Why this server?
Supports containerized deployment of the Chronulus MCP server using Docker images
Why this server?
Packaged as a Docker container for easy deployment and configuration across environments, with various tags for stable and development versions
Why this server?
Enables containerization of the MCP server, allowing it to run as a Docker container with configurable environment variables and exposed ports.
Why this server?
Offers Docker configuration for containerized deployment of the MCP Firebird server alongside a Firebird database, with detailed Dockerfile and docker-compose examples for production use.
Why this server?
Provides containerization for the MCP server with Docker Compose support, including integration with the rqbit torrent client in the same container setup.
Why this server?
Provides a containerized deployment option with preconfigured DNS settings (using quad9) to bypass common connection issues when accessing torrent sites
Why this server?
Provides containerized deployment of the YggTorrent MCP server with Docker and Docker Compose for easy setup and isolation.
Why this server?
Docker support is in progress as mentioned in the 'In Progress' section
Why this server?
Provides containerized deployment options for running the Anubis MCP server with isolated storage using Docker volumes
Why this server?
Allows containerized deployment of the MCP server using Docker, with configuration through environment variables and port publishing.
Why this server?
Provides an alternative deployment method for running the Dart MCP server in a containerized environment.
Why this server?
Supports containerized deployment through Docker, allowing the memory server to be run in isolated containers with appropriate build and run commands.
Why this server?
Offers containerized deployment of the IT tools suite, with support for persistent data volumes and programmatic usage through Docker containers
Why this server?
Provides search capabilities for Docker documentation to help with containerization queries
Why this server?
Provides containerized deployment of the MCP server, with support for mounting host directories as read-only or read-write volumes, allowing secure file operations from within Docker containers.
Why this server?
Provides Docker container deployment option, allowing users to run the PDF reader MCP server in an isolated environment with project directory mounting.
Why this server?
Enables containerization through Docker configuration generation and deployment automation
Why this server?
Provides Docker support for running the Kaltura MCP server through pre-built multi-architecture Docker images or building locally with Docker Compose.
Why this server?
Provides containerized deployment options for the SEQ MCP server, supporting various environment configurations and networking setups for connecting to SEQ instances.
Why this server?
Supports deployment and execution as a Docker container, with ability to configure environment variables for the Inspire API and image paths.
Why this server?
Provides a containerized deployment option for the Yahoo Finance MCP server, allowing users to run the server in an isolated environment without installing dependencies.
Why this server?
Provides Docker-based deployment options for running the MCP server in a containerized environment, with configuration examples for both VS Code and Claude Desktop.
Why this server?
Supports containerized deployment of the ChEMBL MCP server, allowing users to run the server in an isolated environment with all dependencies.
Why this server?
Supports running and extending the proxy as a Docker container, with instructions for creating custom Docker images and Docker Compose setup.
Why this server?
Enables containerized deployment of the MCP server through Docker images
Why this server?
Allows deploying and running the Nanoleaf MCP server in a containerized environment for easier setup and network access
Why this server?
Generates production-ready Dockerfiles with multi-stage builds, security features, and optimization
Why this server?
Allows running the DevBrain MCP server as a Docker container for containerized deployment and integration with Claude
Why this server?
Supports running the MCP server in a Docker container, providing an isolated environment with all dependencies for the Lara Translate integration.
Why this server?
Provides containerized deployment option with official Docker images available on Docker Hub and GitHub Container Registry for running the server in a containerized environment.
Why this server?
Supports running the MCP server over Docker with volume mounting capabilities
Why this server?
Allows to create Railway services from Docker images.
Why this server?
Provides deployment options through Docker containers, allowing the MCP server to be containerized and run in various environments.
Why this server?
Provides Docker support for containerizing and running the Zabbix MCP server with Docker Compose or as a standalone Docker image.
Why this server?
Optional containerization platform for deploying the MCP server in an isolated environment.
Why this server?
Enables deployment of the MCP server via Docker containers, providing an alternative installation method
Why this server?
Offers containerized deployment of the MCP server, simplifying installation and providing consistent runtime environments.
Why this server?
Enables deployment of a WikiJS instance for testing through Docker Compose.
Why this server?
Supports containerized deployment of the prompts MCP server with volume mounting for prompt storage
Why this server?
Provides Docker images for both License API and Management API servers, enabling containerized deployment of the LicenseSpring MCP functionality.
Why this server?
Runs commands within an isolated Docker container environment without giving access to the host Docker daemon.
Why this server?
Provides containerized deployment options with different transport modes (HTTP, SSE) for production and development environments.
Why this server?
Supports containerized deployment of the Docfork MCP server with a provided Dockerfile configuration
Why this server?
Provides containerization support with built-in Docker integration, enabling easy deployment and consistent runtime environment through provided Dockerfile and docker-compose configurations.
Why this server?
Offers a containerized deployment option through Docker, allowing users to run the MCP server in an isolated environment with all dependencies pre-configured.
Why this server?
ATLAS integrates with Docker for simplified installation and running of Neo4j. Docker-compose is included in the repository for self-hosting the Neo4j database.
Why this server?
Offers a containerized deployment option for the MCP server, making it suitable for Docker environments when running in HTTP mode for remote usage.
Why this server?
Supports containerized deployment of the MCP image extraction service through Docker, allowing for isolated and portable execution environments.
Why this server?
Built with containerization in mind, enabling deployment in isolated environments with a pre-built image available for multiple platforms.
Why this server?
Offers containerized deployment of the mindmap conversion service with specific tools for generating either HTML content or files saved to mounted volumes
Why this server?
Provides Docker Compose setup for easily running the required VOICEVOX engine locally.
Why this server?
Supports containerized deployment of the MCP server through Docker, with configuration via environment variables for connecting to Alertmanager instances.
Why this server?
Supports Docker deployment with included Dockerfile and docker-compose configurations for containerized operation.
Why this server?
Allows running the MCP server in a containerized environment with Docker, providing an alternative deployment option with proper isolation and easier environment management.
Why this server?
Provides containerized deployment of MCP servers through Docker, enabling isolated execution environments for dynamically created servers.
Why this server?
Provides containerized deployment of the Postgres MCP server with automatic hostname remapping to work from inside containers on different operating systems.
Why this server?
Provides containerized deployment through Docker Compose, allowing for easier setup and management of the MCP server environment.
Why this server?
Provides tools for checking available tags for Docker container images from Docker Hub
Why this server?
Uses Docker to run GraphDB and provide SPARQL endpoint functionality
Why this server?
Enables running an OpenSearch cluster through Docker Compose for development and testing purposes, with a preconfigured 3-node cluster setup.
Why this server?
Provides deployment option for running the Memory Bank MCP Server in a containerized environment
Why this server?
Allows running the MCP server as a Docker container, providing an alternative deployment method to the npm package.
Why this server?
Enables running the MCP server in a containerized environment with Docker, maintaining Kaggle API credentials through environment variables.
Why this server?
Offers pre-built Docker images available through Docker Hub and GitHub Container Registry for containerized deployment.
Why this server?
Provides capabilities to search for Docker images on Docker Hub and retrieve detailed information about specific images and tags.
Why this server?
Provides secure code execution in isolated Docker containers, used for safely running user-provided code snippets.
Why this server?
Provides tools for running the ORAS MCP Server inside a Docker container, making deployment and execution straightforward without local installation requirements.
Why this server?
Provides containerized deployment of the MCP server, supporting both interactive stdio mode and Streamable HTTP mode with port mapping.
Why this server?
Provides containerized deployment options with pre-built Docker images that can be pulled from Docker Hub, along with Docker Compose configurations for easier setup.
Why this server?
Provides integration with Docker through the devcontainers CLI, enabling tools to initialize, start, and execute commands within development containers for consistent development environments.
Why this server?
Supports deployment as a Docker container, allowing the Monday.com MCP server to be run in containerized environments.
Why this server?
Provides a Docker deployment option with path mapping capabilities to enable file operations between the host and container when using storage-related commands.
Why this server?
Offers a containerized deployment option that communicates with Unity over the network.
Why this server?
Supports containerized deployment of the BICScan MCP Server, enabling easy setup and isolation of the server environment.
Why this server?
Offers Docker deployment support, making it easy to containerize and deploy the MySQL MCP server in various environments.
Why this server?
Supports containerized deployment through Docker, with configuration options for running the MCP server as a Docker container.
Why this server?
Runs as a containerized service with special configurations for host connectivity, allowing MySQL database access from Docker environments with proper networking setup.
Why this server?
Supports Docker-based deployment using docker-compose for containerized production environments
Why this server?
Provides Docker setup and deployment options for running the MCP server with Docker Compose, including build, run, and monitoring commands.
Why this server?
Supports running the code assistant server in a Docker container, with specific configuration instructions for integration
Why this server?
Provides Docker container deployment for the Valyu MCP server, allowing users to run the server in an isolated environment.
Why this server?
Offers containerized deployment of the MCP server with a REST API exposed on port 9097, enabling seamless integration with Docker environments.
Why this server?
Provides configuration support for connecting to Chrome running in Docker containers, with specific setup instructions for containerized environments.
Why this server?
Provides Docker-based setup for easy deployment of the MCP server, with Docker Compose support for building, running and managing the server container.
Why this server?
Enables container and Docker Compose stack management, including creation of standalone containers, deployment of compose stacks, retrieval of container logs, and listing of container status and information.
Why this server?
Enables execution of code in Docker containers, allowing LLMs to run isolated code environments for data processing or computation tasks.
Why this server?
Provides Docker-based deployment option for running the MCP server, with environment variable configuration for authentication.
Why this server?
Enables running the MCP server in a containerized environment, with configuration options for passing API credentials and environment variables to the Docker container.
Why this server?
Provides container-based deployment options with instructions for extending the base image and running via Docker Compose
Why this server?
Offers production-ready containers with compose configurations for simplified deployment and operation.
Why this server?
Provides containerization for the filesystem MCP server, allowing secure access to specified directories through Docker mounts. The README includes Docker configuration examples.
Why this server?
Enables running the MCP server in a container with configurable environment variables, simplifying deployment and dependency management across different environments.
Why this server?
Supports deployment using Docker and Docker Compose for containerized deployment
Why this server?
Enables running the Tigris MCP server in a Docker container for improved security and sandboxing
Why this server?
Enables runtime security analysis of containers, including process behavior monitoring, baselines, and container inventory management.
Why this server?
Supports containerized deployment, allowing AI systems to run YepCode processes in isolated Docker environments.
Why this server?
Enables the execution of containerized MCP servers, particularly used for running the GitHub MCP server and potentially other tool integrations.
Why this server?
Provides containerized deployment of the MCP server through Docker, with environment variable configuration for Kibela authentication.
Why this server?
Provides the ability to proxy any Docker API requests, allowing for complete management of Docker containers, images, networks, and other resources.
Why this server?
Generates Docker configurations (Dockerfile and docker-compose.yml) to containerize and run the mock API servers
Why this server?
Supports containerization of the SSE server for isolated and portable deployment of the Tavily MCP server.
Why this server?
Provides a containerized version of the time MCP server that can be run via Docker to access timezone information and conversion capabilities
Why this server?
Supports running Planka in Docker containers for easy deployment and configuration
Why this server?
Enables running the filesystem MCP server in a containerized environment with volume mounting to control access to specific directories on the host system.
Why this server?
Supports deployment of the MCP server in Docker containers for production environments, with configuration options for environment variables and Claude Desktop integration.
Why this server?
Supports running ChromaDB via Docker for persistent vector storage and advanced RAG capabilities when analyzing theatrical scripts
Why this server?
Supports containerized deployment of the MCP server using Docker, with instructions for building and running the container.
Why this server?
Provides containerization support for the Hunter.io MCP server with Docker Compose setup.
Why this server?
Provides containerization of the MCP server for consistent deployment environments and simplified operations.
Why this server?
Supports containerized deployment of the MCP server for production environments.
Why this server?
Supports containerized deployment using Docker for production environments
Why this server?
Supports deployment through Docker for production environments, with a bundled minimal Docker setup for containerized operation.
Why this server?
Provides containerized deployment options through Docker, including GitHub Container Registry integration
Why this server?
Provides containerized deployment of the MCP server through Docker, with support for Docker Compose to easily run both the ThingsPanel MCP server and MCP Inspector for debugging.
Why this server?
Supports containerized deployment of the MCP server for simplified integration and consistent environment.
Why this server?
Offers containerized deployment of the Illumio MCP server with configuration options for environment variables, volume mounting, and integration with Claude Desktop.
Why this server?
Supports containerized deployment with various methods for environment variable injection, allowing secure configuration of credentials for production environments.
Why this server?
Enables deployment of the MCP server using Docker Compose for containerized setup and management.
Why this server?
Enables containerized deployment of the MCP server with ready-made scripts for building, pushing, and deploying Docker images.
Why this server?
Provides containerized deployment of the server with Docker, allowing isolated execution with proper credential configuration.
Why this server?
Supports containerized deployment of the Korea Weather MCP server, allowing for isolated and consistent execution across different environments.
Why this server?
Integrates with Docker to run the WebSearch Crawler API service, which handles the actual web searches and retrieves results from the internet
Why this server?
Supports integration patterns for deploying the storage server within Docker containers as mentioned in the integrations guide.
Why this server?
Provides containerization support for easier deployment and isolated execution of the MCP server
Why this server?
Supports containerized deployment of the Sharepoint MCP server with Docker, enabling portable and isolated execution
Why this server?
Enables management of Docker containers through the Sakura Cloud AppRun platform, allowing users to create, update, start, stop, and delete containerized applications with custom Docker images.
Why this server?
Allows running the FalkorDB MCP server in a containerized environment with network configuration for connecting to FalkorDB instances.
Why this server?
Allows running the MCP server as a Docker container for easy deployment and usage.
Why this server?
Allows running the MCP server in a Docker container for containerized deployment.
Why this server?
Used for publisher release management and versioning of Netskope components, with capabilities to configure and deploy specific Docker tags for upgrade profiles.
Why this server?
Allows managing Docker containers through natural language commands, including operations such as creating, starting, stopping, and monitoring containers.
Why this server?
Supports containerized deployment with multi-platform support for Linux/amd64, Linux/arm64, and Linux/arm/v7, allowing easy configuration via environment variables or command line arguments.
Why this server?
Future planned integration for server execution and lifecycle management through Docker
Why this server?
Supports hosting Ubuntu24 containers for creating stable environments to run AI models.
Why this server?
Supports deployment through Docker and Docker Compose with preconfigured containers for both the MCP server and Neo4j database
Why this server?
Planned containerization support for deploying the NetBox MCP server in isolated environments.
Why this server?
Recommended method for self-hosting Convex using Docker containers
Why this server?
Provides Docker support for running and testing the MCP server with the Model Context Protocol inspector tool.
Why this server?
Supports containerized deployment of the Backlog MCP server for easy installation and usage.
Why this server?
Allows deploying the PRIMS server in a containerized environment for isolation and reproducibility
Why this server?
Enables scanning of container images for vulnerabilities and malicious packages, supporting both remote registry images and local image tarballs.
Why this server?
Offers containerized deployment of the ToolFront MCP server through Docker images
Why this server?
Supports running ComfyUI in Docker containers, with configuration examples for connecting to containerized ComfyUI instances.
Why this server?
Provides containerized deployment of the TianGong AI MCP Server, allowing for isolated and portable execution of the server with Docker.
Why this server?
Uses Docker for container isolation as a security layer when executing tools on behalf of AI systems.
Why this server?
Provides containerization support for running the MCP Internet Speed Test server in an isolated environment, with Docker configuration for building and deploying the service.
Why this server?
Provides deployment options for running MCPX through containerization, with official Docker images available for easy setup.
Why this server?
Provides containerization support for running BrowserLoop in isolated environments with Docker, ensuring consistent execution across different systems.
Why this server?
Offers integration with Docker Desktop Kubernetes clusters, allowing resource management and operations through the registered Docker Desktop cluster configuration.
Why this server?
Securely runs Python code in isolated Docker containers for safe execution of user and LLM-provided code.
Why this server?
Runs Python code in isolated Docker containers for secure execution, enabling safe installation of packages and execution of arbitrary Python code
Why this server?
Provides containerized deployment with Docker, making it easy to run the MCP server in isolated environments with proper configuration through environment variables.
Why this server?
Enables deployment and configuration of the MCP server through Docker and Docker Compose, with specific settings for networking and container management.
Why this server?
Uses Docker to run the Qdrant vector database which stores the persistent memories created by the model.
Why this server?
Provides containerized deployment of the Materials Project MCP server, making it easy to run the server regardless of the host environment.
Why this server?
Provides Docker environment management for remote servers, enabling execution of commands within containers.
Why this server?
The README includes detailed Docker deployment instructions, allowing the MCP server to be containerized and run in a Docker environment with specified environment variables and ports.
Why this server?
Offers Docker deployment support with a pre-configured Docker image, allowing containerized execution of the IMDb MCP server with proper environment variable configuration.
Why this server?
Supports containerized deployment using Docker for running the OpenFGA MCP server in isolated environments
Why this server?
Provides official Docker images for containerized deployment of the MCP server
Why this server?
Provides support for running Chrome instances in Docker containers, automatically discovering and connecting to Chrome debugging ports in containerized environments.
Why this server?
Offers a Docker container for easy deployment and running of the Root Signals MCP Server.
Why this server?
Provides production-ready Docker deployment configurations with multi-process support and resource management optimizations
Why this server?
Supports running Qdrant in a Docker container for local vector database storage and querying
Why this server?
Offers ready-to-use Docker containers for all transport methods (stdio, SSE, HTTP Streaming).
Why this server?
Required for code generation during development, used to generate API client/server schemas for the TouchDesigner integration.
Why this server?
Supports containerized deployment for secure isolation of shell command execution
Why this server?
Provides containerized deployment of the MCP-Stockfish server, making it easier to run in isolated environments without affecting local configurations.
Why this server?
Provides containerized execution environment for the MCP server, allowing for isolated and consistent deployment across different systems.
Why this server?
Provides containerized deployment of the UniProt MCP server with multi-stage builds and security best practices
Why this server?
Provides Docker container deployment options for running the DBHub server with configurable database connections and transport options.
Why this server?
Supports containerized deployment via Docker, allowing Claude to safely access Kuzu databases with proper volume mounting and configuration.
Why this server?
Supports containerized deployment with Docker, including health checks and monitoring for production environments.
Why this server?
Enables running the Playwright MCP server in a containerized environment with headless Chromium support.
Why this server?
Offers deployment options through Docker containers, with health monitoring endpoints and environment variable configuration for the Unimus MCP server.
Why this server?
Provides containerized deployment of the WebP batch conversion service, allowing users to run the converter in an isolated environment with volume mounting for image processing.
Why this server?
Enables deployment of the MCP server using Docker, allowing containerized hosting of the Biel.ai documentation integration service
Why this server?
Offers containerized deployment options for running the Short Video Maker, including specialized images for CPU and NVIDIA GPU acceleration.
Why this server?
Provides Docker container deployment options for easy setup and consistent runtime environments.
Why this server?
Enables launching and managing Docker containers as backend MCP servers, allowing containerized tool execution and isolation
Why this server?
Provides containerization support for deploying the Nexonco MCP server as an alternative to local installation
Why this server?
Offers containerization support with a provided Dockerfile to build and run the MCP server in an isolated environment with proper dependencies.
Why this server?
Enables interaction with Docker containers through a dedicated MCP, allowing for container management operations.
Why this server?
Supports containerized deployment of the domain analysis server for easier distribution and scaling.
Why this server?
Offers containerized deployment options for running the MCP server across different environments, with specific configuration instructions for Linux, macOS and Windows systems.
Why this server?
Provides a containerized deployment option for the MCP server, with Oracle Client libraries pre-installed for connecting to Oracle databases
Why this server?
Supports containerized deployment through Docker, allowing the MCP server to run in isolated environments with configurable settings through environment variables.