python-dependency-manager-companion

This MCP server is a companion image for helping with Python dependency management within MCP-enabled IDEs. It exposes guidance and tooling around popular Python package managers such as pip, conda, poetry, uv, pixi, and pdm. When queried through your MCP setup, it can provide current syntax, migration help, and best-practice usage for installing, updating, and resolving dependencies across these tools. The server is designed to be queried via the MCP pipeline and relies on the underlying Docker image keminghe/py-dep-man-companion to run the actual commands and return results.

To use it, deploy the Docker image in your environment and reference it in your mcp.json under a server entry (as shown in the example). You can then ask the assistant questions like: How do I migrate a conda project to uv? What is the recommended command to install a package with pdm? How do I pin a specific Python version when using poetry? The tool will guide you with up-to-date syntax and command examples drawn from official docs.

Prerequisites:

• Docker (or another container runtime compatible with the image)
• Internet access to pull the image

Installation steps:

1. Install Docker on your operating system. Follow the official docs for your platform: https://docs.docker.com/get-docker/
2. Pull the MCP companion image: docker pull keminghe/py-dep-man-companion
3. Integrate with MCP: add the server reference to your mcp.json as shown in the Quick Start. Example entry: { "mcp": { "servers": { "python-deps": { "command": "docker", "args": ["run", "-i", "--rm", "keminghe/py-dep-man-companion"] } } } }
4. Run and test: ensure your MCP client can communicate with the server and respond to queries about Python dependency management.

Notes and caveats:

• This MCP server is Archived and no longer maintained. While the Docker image may still work, rely on official package manager docs for critical updates.
• The image keminghe/py-dep-man-companion covers guidance for pip, conda, poetry, uv, pixi, and pdm; verify compatibility with your environment and the specific versions you use.
• If you encounter issues, check the container runtime logs and ensure network access to any external resources referenced in guidance.
• Environment variables are not pre-defined in the default setup; if needed, customize the container invocation to mount configs or pass tokens per your environment.