python-setup vs PEP 621 project name shape, body discarded
python-setup is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
python-setup is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. PEP 621 project name shape, body discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  PEP 621 project name shape, body discarded | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | python-setupno longer listed · | PEP 621 project name shape, body discarded |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/pep621-ok/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/sadri-dridi/named-mcp-utilities |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of python-setup
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Python development toolkit with UV for fast package management, project structure, and dependency management. Includes python expert agent for strategic Python architecture…
-
Persistent memory, shared standards, and structured workflows for AI coding agents
-
Developer environment bootstrap generator for Claude Code. Scans a project for signal files (requirements.txt, package.json, Cargo.toml, Dockerfile, etc.), detects the tech stack…
-
Use this agent when working with Python code that requires advanced features, performance optimization, or comprehensive refactoring. Examples: <example>Context: User needs to…
-
Opinionated Python 3.13+ application and library design guidance.
-
Makes a repo agent-ready with AGENTS.md, boundary tests, CI pipeline, and GC scripts based on OpenAI's harness engineering methodology
What each says it does
python-setup
Generate Python project setup with pyproject.toml and linting
PEP 621 project name shape, body discarded
PEP 621 project name shape, body discarded
How to run each
python-setup
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PEP 621 project name shape, body discarded As a remote MCP server
claude mcp add --transport http pep621-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/pep621-ok/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PEP 621 project name shape, body discarded has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: python-setup · What it can do: PEP 621 project name shape, body discarded · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.