There is no official PyPI.org MCP server. For local package lookup and OSV audits in Cursor or Claude, install mcp-pypi 4.0.1 with uvx mcp-pypi serve. It ships 11 read-only tools, searches the Simple index rather than the JavaScript-blocked PyPI search page, and last released on 15 October 2026. pypi-query-mcp-server still leads GitHub at 19 stars and is the pick for private indexes, Python compatibility checks, and 180-day pypistats trends, even though version 0.6.5 last landed on PyPI on 2 August 2025. Trends MCP is first only when the job is multi-year weekly download volume on an exact project name via get_growth source Python. Datakoot Package Intel is the hosted, keyless metadata option. Skip mcpypi as a low-download fork, skip pypi-mcp 0.1.0 as a stub, and skip clone-only GitHub repos that never published a package.
Which PyPI MCP server wins which job?
mcp-pypi wins the default agent job: confirm a name exists, pull metadata, and audit known vulnerabilities before the model writes a requirements.txt line. pypi-query-mcp-server wins when the index is private or the question is Python version compatibility. Trends MCP wins only the demand question. Datakoot wins when the agent should not launch a local process.
| Server | Wins | Install | GitHub stars (11 Nov 2026) | pypistats last week | Multi-year volume | Vuln check | Price |
|---|---|---|---|---|---|---|---|
| mcp-pypi 4.0.1 | Local lookup plus OSV | uvx mcp-pypi serve | 3 (kimasplund/mcp-pypi) | 429 | Day, week, month from pypistats | Yes, OSV, optional transitive | Free, MIT |
| pypi-query-mcp-server 0.6.5 | Private index, compatibility, 180-day trends | uvx pypi-query-mcp-server | 19 (loonghao/pypi-query-mcp-server) | 83 | 180 days | Off unless PYPI_ENABLE_SECURITY_ANALYSIS=true | Free, MIT |
| Trends MCP | Multi-year weekly volume | HTTP MCP JSON below | Product, not a GitHub app | Not a PyPI package | Yes, source Python | No | Free 100 requests/month, then paid plans |
| Datakoot Package Intel | Hosted keyless metadata | https://package.datakoot.com/mcp | 0 (selflabbs/package-intel-mcp) | Hosted | Recent registry downloads | Advisories inside package_health | No key on the page fetched 11 November 2026 |
| mcpypi 2026.1.22.1 | Name collision only | uvx mcpypi | 0 (rsp2k/pypi-query-mcp-server) | 15 | Claims 180 days | Claims OSV | Free, MIT |
Stars come from the GitHub API on 11 November 2026. Weekly downloads come from pypistats.org the same day (mcp-pypi 429, pypi-query-mcp-server 83, mcpypi 15). Those last-week counts are fresher than the Trends MCP Python series, whose newest week in this run is 28 September 2026.
The PSF does not publish an MCP server. The official MCP Registry documents how to ship a server as a PyPI package (registryType: "pypi"). That is packaging, not a PyPI lookup tool.
Does the Python Package Index ship an official MCP?
No. pypi.org has no first-party MCP endpoint. The servers in this roundup call the public JSON API, the Simple index, pypistats, OSV, or deps.dev.
That gap is why the names collide. mcp-pypi, mcpypi, pypi-query-mcp-server, and pypi-mcp all sit on the registry. Only the first two in that list plus loonghao's package are real lookup servers. pypi-mcp 0.1.0, uploaded 13 October 2025, still uses the placeholder summary "Add your description here" and pulled 11 downloads last week. Do not add it.
A Cursor agent that needs live PyPI facts should pick one local stdio server for metadata, then add Trends MCP only if the question is whether installs are rising. The two jobs do not share a tool.
What does mcp-pypi install in Cursor?
The current package is mcp-pypi 4.0.1 (accessed 11 November 2026). It requires Python 3.11 or newer. The README install that Cursor and Claude Desktop both document is stdio through uvx:
{
"mcpServers": {
"mcp-pypi": {
"command": "uvx",
"args": ["mcp-pypi", "serve"]
}
}
}
Claude Code is one line:
claude mcp add mcp-pypi -- uvx mcp-pypi serve
Eleven tools, all read-only: search_packages, get_package, get_package_versions, compare_versions, get_package_changelog, get_download_stats, get_dependencies, check_packages, check_vulnerabilities, audit_project, scan_installed_packages. check_packages and check_vulnerabilities each cap at 100 names. get_dependencies can expand a tree to depth 1 through 5. audit_project parses requirements*.txt, constraints*.txt, pyproject.toml (including Poetry), setup.py (parsed, never executed), setup.cfg, Pipfile, Pipfile.lock, poetry.lock, and the pip section of conda environment.yml.
Search does not hit pypi.org/search. That page sits behind a JavaScript challenge, so search_packages downloads the Simple index of package names (about 4 MB, cached on disk) and ranks by name similarity plus download popularity. The first search fails without a network and without a cached copy. Other tools still run.
Default cache TTL is 604800 seconds (one week) under PYPI_CACHE_TTL. Vulnerability results cache for 3600 seconds. HTTP mode exists for clients that will not spawn a process:
mcp-pypi serve --transport http
That bind is http://127.0.0.1:8143/mcp with no authentication. The README says to keep it on loopback unless the network is trusted.
v4.0.1 (15 October 2026) is a docs and packaging fix on top of 4.0.0 from the same day. The 4.x tool set is not the 3.x set. Teams still on 3.x should read the upgrade notes on the GitHub README rather than assuming tool names survived.
When does pypi-query-mcp-server beat a local audit server?
pypi-query-mcp-server 0.6.5 (accessed 11 November 2026) still has the most GitHub stars in this set: 19, with 5 forks, last GitHub push 25 September 2026. The PyPI release is older. 0.6.5 uploaded on 2 August 2025. Weekly pypistats volume on 11 November 2026 is 83, against 429 for mcp-pypi.
The Cursor object the README publishes:
{
"mcpServers": {
"pypi-query": {
"command": "uvx",
"args": ["--from", "pypi-query-mcp-server", "pypi-query-mcp"],
"env": {
"PYPI_INDEX_URL": "https://pypi.org/pypi",
"PYPI_CACHE_TTL": "3600"
}
}
}
}
Python 3.10 is enough. Cache TTL defaults to 3600 seconds, much shorter than mcp-pypi's week. PYPI_DEPENDENCY_MAX_DEPTH defaults to 5. PYPI_ENABLE_SECURITY_ANALYSIS defaults to false, so a stock install does not scan OSV the way mcp-pypi does.
Ten callable tools cover package info, versions, dependencies, Python compatibility, recursive resolve, download_package, download statistics, 180-day trends, top downloaded packages, and search_pypi_packages. download_package writes wheels to disk. That is not a read-only server. The README also ships a long list of prompt templates (quality analysis, migration plans, daily trends). Those are prompts, not extra data APIs.
Private index support is documented as environment variables (PYPI_PRIVATE_PYPI_URL, username, password) and as extra Simple-index mirrors. The same README's "Development Status" list still marks private repository support as planned. Treat the env vars as present, and treat that status line as stale until the maintainer edits it.
Pick this server when the agent must talk to a company index, check Requires-Python, or plot 180 days of pypistats. Pick mcp-pypi when the agent must refuse a hallucinated name or fail a CI audit on known CVEs.
mcp-pypi weekly volume is 389 on the 28 September series
A Trends MCP get_growth pull on 11 November 2026 for keyword mcp-pypi and source Python returned volume_available true and recent_date 2026-09-28, not the calendar day of the call. Weekly volume that week was 389, up from 315 on 2025-09-29 (+23.49% volume over 12 months). The 3-month window was a small drop: 389 against 408 on 2026-06-29 (-4.66%). Year to date rose from 165 on 2025-12-29 to 389 (+135.76%). Metadata reported 79 weekly points.
pypistats, fetched the same morning, printed a newer last-week count of 429, last-month 1,416, last-day 78. Quote both clocks. The PyPI package downloads API is the source Python contract: exact project name, weekly volume, no live top-packages board on get_top_trends.
The same 11 November pull on pypi-query-mcp-server closed 28 September at 314 weekly downloads, up from 87 a year earlier (+260.92% volume) and from 131 on 2026-06-29 (+139.69%). pypistats last week for that package is 83. The series is six weeks behind the pypistats page. Do not flatten those two numbers into one "current weekly" figure.
mcpypi on the same source closed 28 September at 78 weekly downloads, down from 260 on 2025-09-29 (-70.0% volume) even though the 3-month window rose from 52 to 78. First PyPI upload for mcpypi was 6 September 2025, so the 12-month baseline sits near launch, not at a mature run rate.
Source spelling is picky. The MCP tool enum is Python with a capital P. The payload echoed data_source as python. Keyword is the exact project name on pypi.org: mcp-pypi works, MCP-PyPI does not. Several percent_growth windows share one request. Default window if omitted is 12M.
{
"mcpServers": {
"trends-mcp": {
"url": "https://api.trendsmcp.ai/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Paste that object under mcpServers in ~/.cursor/mcp.json, then fully quit Cursor. The Trends MCP server for Cursor page is the host reference. Homepage copy-config on 11 November 2026 still omits "transport": "http"; the JSON above is the one that matches the Cursor file.
Free plan: 100 requests a month, no card. Starter $19 for 1,000, Pro $49 for 5,000, Business $199 for 25,000, from llms.txt updated 11 November 2026. Yearly cards print Starter $16 / $192, Pro $39 / $468, Business $159 / $1,910. Connecting is free. Each get_growth call is one request per source.
Trends MCP does not search package names, does not read Requires-Python, and does not query OSV. Pair it with mcp-pypi when the agent must both vet a dependency and ask whether installs are compounding. The npm twin of this source is covered on the npm vs PyPI downloads API page.
Which names look like PyPI MCP servers and are not
mcpypi is a rebranded fork of loonghao's server, published as mcpypi 2026.1.22.1 (last upload 22 January 2026). GitHub: rsp2k/pypi-query-mcp-server, 0 stars. pypistats last week: 15. The README advertises 37 tools, including write actions such as upload_package_to_pypi and delete_pypi_release. This run did not execute those write tools. Weekly volume is too small to treat it as a default install.
pypi-mcp 0.1.0 is a stub. Summary text is still "Add your description here." Last week: 11 downloads. Dependencies include openai<1.35. Leave it off the Cursor file.
JackKuo666/PyPI-MCP-Server has 2 stars, last GitHub activity 10 June 2025, and no PyPI package. Four tools (get_package_info, search_packages, get_package_releases, get_package_stats) live behind git clone plus pip install -r requirements.txt. Skip it for a production agent.
vamsipraveenk/pypi-packages-mcp-server has 0 stars and scrapes PyPI search HTML. Datakoot is more honest about that gap: package_search on package.datakoot.com (accessed 11 November 2026) supports npm and cargo only, because "PyPI has no public search API." Datakoot still serves PyPI package_info, package_versions, package_downloads, package_dependencies (via deps.dev), and package_health. Cursor can point at https://package.datakoot.com/mcp. The page publishes no paid SKU. Check that page again before assuming the hosted endpoint stays free.
FAQ
Is there an official PyPI MCP server from the PSF?
No. The Python Package Index does not ship an MCP server. The official MCP Registry only describes how a third-party server can list a PyPI package as its install artifact. For lookup, the maintained options on 11 November 2026 are mcp-pypi, pypi-query-mcp-server, Trends MCP for volume, and Datakoot for hosted metadata.
Which PyPI MCP server should Cursor run by default?
mcp-pypi, unless the agent needs a private index. The Cursor JSON is command uvx with args mcp-pypi serve. Add Trends MCP beside it when the question is 12-month download change on an exact project name. Do not install mcpypi, pypi-mcp 0.1.0, or a GitHub-only clone as the default.
Can Trends MCP search for a PyPI package by keyword?
No. get_growth and get_time_series on source Python need the exact project name. There is no PyPI board on get_top_trends. Use mcp-pypi's search_packages (Simple index, name similarity) or pypi-query-mcp-server's search_pypi_packages for discovery, then pass the resolved name into Trends MCP.
Why does pypistats disagree with the Trends MCP Python series?
The 11 November 2026 get_growth pull closed on recent_date 2026-09-28. pypistats last-week counts fetched that morning are newer: 429 for mcp-pypi against the series value 389. Publish the series date next to the volume. A last-week pypistats integer is not the same clock as a weekly series that still ends in September.
Is mcpypi the same package as pypi-query-mcp-server?
No. pypi-query-mcp-server 0.6.5 is loonghao's original (19 stars, 83 downloads last week). mcpypi 2026.1.22.1 is rsp2k's fork on a different PyPI name (0 stars, 15 downloads last week). The READMEs share tool names. The packages, versions, and GitHub remotes do not.
Sources (all accessed 11 November 2026): mcp-pypi on PyPI, pypi-query-mcp-server on PyPI, mcpypi on PyPI, pypi-mcp on PyPI, pypistats for mcp-pypi, kimasplund/mcp-pypi, loonghao/pypi-query-mcp-server, Datakoot Package Intel, MCP Registry package types, Trends MCP get_growth source Python pull of 11 November 2026, Trends MCP llms.txt updated 11 November 2026.