Python/PyPI support for MCP Registry publishing

[cklam12345]

Summary

The current MCP Registry publishing flow (mcp-publisher CLI) only supports TypeScript/npm packages. Python MCP servers published to PyPI have no supported path to the registry.

Current state

The quickstart guide assumes:

• Node.js / TypeScript
• npm as the package registry
• package.json with mcpName field

None of these apply to Python servers.

What's needed

A Python publishing path that supports:

• PyPI as the artifact host (equivalent to npm)
• pyproject.toml as the metadata source (equivalent to package.json)
• mcp-publisher CLI support for pip/uv based projects
• mcpName equivalent field in pyproject.toml (e.g. [tool.mcp] name = "io.github.username/server-name")

Why this matters

The Python MCP ecosystem is growing fast. The mcp Python SDK is already widely used. Several production-quality Python MCP servers exist on PyPI today with no registry path:

• wisdomGraph — Neo4j-native DIKW accumulative memory for Claude Code (88 tests, MIT, v0.2.0)
• Others in the community are blocked on the same issue

Proposed pyproject.toml convention

[tool.mcp]
name = "io.github.cklam12345/wisdomgraph"

This mirrors the mcpName field in package.json and keeps the io.github.* namespace convention.

Request

1. Add Python/PyPI support to mcp-publisher
2. Document the Python publishing path in the quickstart guide
3. Or provide an alternative submission path for PyPI packages in the interim

Happy to help test a Python publishing path or contribute a PR if the architecture direction is shared.

— @cklam12345, author of wisdomGraph