The crypto tool is one file in a project that is mostly scaffolding — settings per environment, schemas, service and resource layers already separated. If what you want is prices, the setup is a key and a run command. If what you want is your own tools against your own API, the interesting part is the structure already sitting around that one tool.
A Python MCP server that answers with cryptocurrency price information, reading from CoinMarketCap. It ships with an environment-based configuration so the same code runs locally, in staging and in production.
- Real-time cryptocurrency price retrieval through the CoinMarketCap API
- Configuration switched by environment — local, development, staging and production each get their own settings
- A Docker image for running it as a container instead of a local process
- A documented pattern for adding your own tools: define the function, register it, document it with a docstring
The project python-server-mcp, version 0.1.0, run from a checkout with uv: `uv venv`, activate it, `uv sync`, then `python main.py` for stdio. Python 3.12 or higher. Two settings go in a `.env` file or the client's env block: `COINMARKETCAP_API_KEY` and `ENVIRONMENT`. The Docker path builds `mcp/python-server-mcp` and passes both variables through.
One command plus a key — docker run -i --rm -p 8000:8000 -e ENVIRONMENT -e COINMARKETCAP_API_KEY mcp/python-server-mcp, then supply credentials