Repository navigation
Audit and document the MCP server publishing experience #1734
Description
Summary
Review and document the end-to-end experience of publishing an MCP server to PyPI, identifying friction points and opportunities for improvement.
Motivation
- Many users ask questions about how to properly package and publish their MCP servers
- The current experience may have unnecessary friction or missing guidance
- Understanding the UX gaps informs what SDK improvements or documentation is needed
Goal
- Document the current publishing workflow step-by-step
- Identify pain points and common mistakes
- Propose improvements (whether docs, tooling, or SDK changes)
Activity
nikitagrover19 commentedon Aug 9, 2026
Hi, I'd like to work on this if it's still open. I went through the current docs first (docs/run/deploy.md, docs/get-started/installation.md, RELEASE.md) and confirmed there's no existing walkthrough connecting "I have a working example server" to "here's how to package and publish it to PyPI" — deploy.md covers hosting/scaling, not packaging. I also noticed the registry publishing guide (mcp-publisher / server.json) is fairly npm-centric with no worked Python/PyPI example, which might be worth covering too.
I'd plan to actually go through the publish flow myself (hatchling build → PyPI → mcp-publisher registry submission) using one of the example servers, document the friction points, and open a docs PR. Used AI assistance to review the existing docs structure before writing this, happy to go deeper on any part you'd like prioritized.
Could you confirm if this is ready to be picked up, or is it waiting on further triage?