Python Dependency Manager Companion
# ⚠️ [Archived] ⚠️ Python Dependency Manager Companion MCP Server
> [!WARNING]
>
> **This repository is archived and no longer maintained.**
>
> - **Archived**: 2026-02-15 by [@KemingHe](https://github.com/KemingHe)
> - **Archive Reason**: Use case too niche + better alternatives i.e. [Context7](https://context7.com/) available
> - **Inquries and Corrections**: Email keminghe[dot]career[at]gmail[dot]com
Stop getting out-of-date Python package manager commands from your AI. Cross-reference latest official [`pip`](https://pip.pypa.io/), [`conda`](https://docs.conda.io/projects/conda), [`poetry`](https://python-poetry.org/), [`uv`](https://docs.astral.sh/uv/), [`pixi`](https://pixi.sh/), and [`pdm`](https://pdm-project.org/) docs with auto-updates. [[Watch Demo on YouTube]](https://youtu.be/3nVp46Q8FdY)
## 🚀 Quick Start for Agentic IDEs
**1. Pull Docker image**:
```shell
# Pin to commit hash for production security
# Get current hash from: https://hub.docker.com/r/keminghe/py-dep-man-companion/tags
docker pull keminghe/py-dep-man-companion@sha256:2c896dc617e8cd3b1a1956580322b0f0c80d5b6dfd09743d90859d2ef2b71ec6 # 2025-07-22 release example
# Or use latest for development
docker pull keminghe/py-dep-man-companion:latest
```
**2. Add to your IDE's `mcp.json`**:
```json
{
"mcp": {
"servers": {
"python-deps": {
"command": "docker",
"args": ["run", "-i", "--rm", "keminghe/py-dep-man-companion"]
}
}
}
}
```
**3. Ask package manager questions** - "How to migrate a `conda` project to `uv`?" and get accurate, current official syntax.
## 🤝 Contributing
**Use as template**: [[Create from template]](https://github.com/new?template_name=python-dependency-manager-companion-mcp-server&template_owner=KemingHe) for your own MCP server projects.
**Contribute back**: Fork and follow [CONTRIBUTING.md](./CONTRIBUTING.md) for development setup.
## 🔄 Auto-Update Architecture
1. ⏰ **Every Tuesday 6pm ET**
2. 📚 **Sync Official Docs**
3. 🔍 **Rebuild Search Index**
4. 🐳 **Publish Latest Image**
## 🗺️ Roadmap
- [x] Added support for `pixi` and `pdm` in version 0.1.1
- [ ] Add comprehensive tests with 100% coverage
- [ ] Add indexing support for PDF and CSV files
## 📁 Project Structure
```plaintext
python-dependency-manager-companion-mcp-server/
├── .github/workflows/ # Automation workflows
│ ├── auto-update-docs.yml # Weekly docs update
│ ├── auto-update-index.yml # Search index rebuild
│ ├── auto-update-publish.yml # Multi-arch Docker publish
│ ├── auto-update.yml # Combined automation
│ └── README.md # Workflow documentation
├── src/
│ ├── assets/ # Documentation source files
│ │ ├── conda/ # conda docs
│ │ ├── pip/ # pip docs
│ │ ├── poetry/ # poetry docs
│ │ ├── uv/ # uv docs
│ │ ├── pixi/ # pixi docs
│ │ └── pdm/ # pdm docs
│ ├── index/ # Pre-built search index
│ ├── build_index.py # Tantivy index builder
│ └── mcp_server.py # FastMCP stdio server
├── Dockerfile # Container build configuration
├── pyproject.toml # Project dependencies and metadata
└── uv.lock # Locked dependencies
```
## 📄 License
This project is licensed under the [MIT License](./LICENSE) - a permissive license that allows free use, modification, and distribution with attribution.
## 📞 Support
Open a [GitHub issue](https://github.com/KemingHe/python-dependency-manager-companion-mcp-server/issues) for bug reports and feature requests.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clearly defined purpose: searching Python dependency manager documentation. No other tools exist to cause ambiguity.
The single tool name 'search_py_dep_man_docs' follows a clear verb_noun pattern (search + py_dep_man_docs). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
One tool is too few for a server named 'Python Dependency Manager Companion,' which suggests a broader scope like managing dependencies, not just searching docs. A single search tool feels thin and incomplete for the implied domain, lacking operations like installing, updating, or listing dependencies.
The tool surface is severely incomplete for the server's purpose. While the search tool is well-described, there are significant gaps: no tools for actual dependency management tasks (e.g., install, update, remove, list dependencies), version checking, or environment management. This will cause agent failures when trying to perform core dependency management workflows.