Containerize MCP Server

Package R MCP server into Docker container for portable deployment.

When Use

• Deploy R MCP server without requiring local R installation
• Create reproducible MCP server environment
• Run MCP servers alongside other containerized services
• Distribute MCP server to other developers

Inputs

• Required: R MCP server implementation (mcptools-based or custom)
• Required: Docker installed, running
• Optional: Additional R packages server needs
• Optional: Transport mode (stdio or HTTP)

Steps

Step 1: Create Dockerfile for MCP Server

FROM rocker/r-ver:4.5.0

# Install system dependencies
RUN apt-get update && apt-get install -y \
    libcurl4-openssl-dev \
    libssl-dev \
    libxml2-dev \
    libgit2-dev \
    libssh2-1-dev \
    git \
    curl \
    && rm -rf /var/lib/apt/lists/*

# Install R packages
RUN R -e "install.packages(c( \
    'remotes', \
    'ellmer' \
    ), repos='https://cloud.r-project.org/')"

# Install mcptools
RUN R -e "remotes::install_github('posit-dev/mcptools')"

# Set working directory
WORKDIR /workspace

# Expose MCP server ports
EXPOSE 3000 3001 3002

# Environment variables
ENV R_LIBS_USER=/workspace/renv/library
ENV RENV_PATHS_CACHE=/workspace/renv/cache

# Default: start MCP server
CMD ["R", "-e", "mcptools::mcp_server()"]

Got: Dockerfile exists in project root with rocker/r-ver base image, system dependencies, mcptools installation, MCP server as default command.

If fail: Verify base image tag matches your R version. remotes::install_github fails? Check git and libgit2-dev are in system dependencies layer.

Step 2: Create docker-compose.yml

version: '3.8'

services:
  mcp-server:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: r-mcp-server
    image: r-mcp-server:latest

    volumes:
      - /path/to/projects:/workspace
      - renv-cache:/workspace/renv/cache

    stdin_open: true
    tty: true

    network_mode: "host"

    environment:
      - TERM=xterm-256color
      - R_LIBS_USER=/workspace/renv/library

    restart: unless-stopped

volumes:
  renv-cache:
    driver: local

Using network_mode: "host" ensures MCP server ports accessible on localhost.

Got: docker-compose.yml in project root with MCP server service, volume mounts for project files and renv cache, stdin_open/tty enabled for stdio transport.

If fail: Volume paths invalid? Adjust /path/to/projects to actual project directory. On Windows/WSL, use /mnt/c/... or /mnt/d/... paths.

Step 3: Build and Start

docker compose build
docker compose up -d

Got: Container starts with MCP server running.

If fail: Check logs with docker compose logs mcp-server. Common issues:

• Missing R packages: Add to Dockerfile RUN install step
• Port already in use: Change exposed port or stop conflicting service

Step 4: Connect Claude Code to Container

For stdio transport (container must stay running with stdin):

claude mcp add r-mcp-docker stdio "docker" "exec" "-i" "r-mcp-server" "R" "-e" "mcptools::mcp_server()"

For HTTP transport (if MCP server supports it):

{
  "mcpServers": {
    "r-mcp-docker": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Got: Claude Code MCP configuration includes r-mcp-docker server entry. claude mcp list shows new server.

If fail: Stdio transport? Ensure container name matches (r-mcp-server) and container running with docker ps. HTTP transport? Verify port exposed, reachable with curl http://localhost:3000/mcp.

Step 5: Verify Connection

# Check container is running
docker ps | grep mcp-server

# Test R session inside container
docker exec -it r-mcp-server R -e "sessionInfo()"

# Verify mcptools is available
docker exec -it r-mcp-server R -e "library(mcptools)"

Got: docker ps shows r-mcp-server container running. sessionInfo() returns expected R version. library(mcptools) loads without error.

If fail: Container not running? Check docker compose logs mcp-server for startup errors. mcptools fails to load? Rebuild image to ensure package installed correctly.

Step 6: Add Custom MCP Tools

To add project-specific MCP tools, mount R scripts:

volumes:
  - ./mcp-tools:/mcp-tools

Load them in CMD:

CMD ["R", "-e", "source('/mcp-tools/custom_tools.R'); mcptools::mcp_server()"]

Got: Custom R scripts accessible inside container at /mcp-tools/. MCP server loads them on startup alongside default tools.

If fail: Verify volume mount path correct with docker exec -it r-mcp-server ls /mcp-tools/. Scripts fail to source? Check missing package dependencies in custom tools.

Checks

• Container builds without errors
• MCP server starts inside container
• Claude Code can connect to containerized server
• MCP tools respond correctly to requests
• Container restarts cleanly
• Volume mounts allow access to project files

Pitfalls

• stdin/tty requirements: MCP stdio transport requires stdin_open: true and tty: true
• Network isolation: Default Docker networking may prevent localhost access. Use network_mode: "host" or expose specific ports.
• Package versions: Pin mcptools to specific commit for reproducibility
• Large image size: mcptools + dependencies can be large. Consider multi-stage builds for production.
• Windows Docker paths: Running Docker Desktop on Windows with WSL? Path mapping differs

See Also

• create-r-dockerfile - base Dockerfile patterns for R
• setup-docker-compose - compose configuration details
• configure-mcp-server - MCP server configuration without Docker
• troubleshoot-mcp-connection - debugging MCP connectivity issues