Empaquetar el servidor en Docker

To run your server anywhere, you bundle it with its Python and dependencies. Docker wraps all of that into one portable image. 📦

A Dockerfile is a plain recipe of steps. Each line tells Docker how to assemble the image that will eventually run your MCP server.

The first line picks a base image. A slim Python image keeps things small while still giving you a working interpreter to build on.

Use WORKDIR to choose the folder inside the image where your code lives. Later commands run relative to this clean, predictable path.

The COPY instruction moves files from your machine into the image. Bring in your server code and its dependency list together.

Run pip during the build so the mcp SDK and your libraries are baked into the image, not installed fresh on every start.

The CMD line is what runs when the container launches. Point it at your server so the container boots straight into MCP.

One command turns the recipe into a real image. The -t flag tags it with a name you can reuse later. 🛠️

Start a container from your image with docker run. For HTTP servers, map a port so the outside world can reach it.

Smaller images deploy faster and have less to attack. Skip caches and only copy what you need to keep the build lean.

Anyone who pulls your image gets the exact same environment you built. That reproducibility ends the classic it-works-on-my-machine problem.

Which Dockerfile line decides what runs when the container starts?

A Dockerfile picks a base, copies code, installs deps, and sets a start command. Build it into an image and run it the same way anywhere. 🚀