Would be cool if you had a Docker image for this server, makes it easy to test with the Chinook database. Something like this:
# Use a Python image with uv pre-installed
FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
# Install the project into `/app`
WORKDIR /app
# Enable bytecode compilation
ENV UV_COMPILE_BYTECODE=1
# Copy from the cache instead of linking since it's a mounted volume
ENV UV_LINK_MODE=copy
# Install the project's dependencies using the lockfile and settings
RUN --mount=type=cache,target=/root/.cache/uv \
--mount=type=bind,source=uv.lock,target=uv.lock \
--mount=type=bind,source=pyproject.toml,target=pyproject.toml \
uv sync --frozen --no-install-project --no-dev
# Then, add the rest of the project source code and install it
# Installing separately from its dependencies allows optimal layer caching
COPY . /app
RUN --mount=type=cache,target=/root/.cache/uv \
uv sync --frozen --no-dev
ENV DB_URL=sqlite:////app/tests/Chinook_Sqlite.sqlite
# Place executables in the environment at the front of the path
ENV PATH="/app/.venv/bin:$PATH"
# Reset the entrypoint, don't invoke `uv`
ENTRYPOINT []
CMD ["mcp-alchemy"]
Assuming that is tagged as 'some-registry/mcp-alchemy:latest', you would then run as:
docker run --interactive --init --rm some-registry/mcp-alchemy
In Claude or whatever, no need to specify DB_URL. Or it could be run with a bind mount to the db file and DB_URL overridden at runtime.
Would be cool if you had a Docker image for this server, makes it easy to test with the Chinook database. Something like this:
Assuming that is tagged as 'some-registry/mcp-alchemy:latest', you would then run as:
In Claude or whatever, no need to specify DB_URL. Or it could be run with a bind mount to the db file and DB_URL overridden at runtime.