Allows querying Python package metadata from the Python Package Index (PyPI), including package information, versions, and dependencies via the PyPI JSON API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-pypi show details for the flask package"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PyPI MCP — wraps the Python Package Index (PyPI) JSON API (free, no auth).
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Get metadata for a Python package on PyPI (the Python Package Index). Returns the latest version, summary, author, license, project URLs, required Python version, keywords, classifiers, and the release artifact files that |
| Get metadata for a specific version of a Python package on PyPI. Returns the summary, required Python version, the full dependency list (requires_dist, i.e. what pip would resolve), and the downloadable files for that version. Use to inspect a pinned release like requests 2.31.0. |
| List all published version strings for a Python package on PyPI, sorted, plus the latest version. Useful to see a package's release history or check which versions are available to pip install. |
| Get recent download counts for a Python package (last day, last week, last month) from pypistats.org. Gauges how popular a pip package is. |
Related MCP server: PyPI Query MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"pypi": {
"url": "https://gateway.pipeworx.io/pypi/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/pypi/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Pypi data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Real-time Python package and vulnerability data for AI coding agents.
Crates.io MCP — wraps the crates.io REST API v1 (free, no auth)
RubyGems MCP — wraps the RubyGems.org public API (free, no auth)
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
