modelcontextprotocol / modelcontextprotocol/python-sdk
Specific transports could be Python package extras
Open
Nobody has claimed this yet.
breaking change
enhancement
needs decision
P3
v2
- Dominant language
- Python
- Stars
- 24.3k
- Forks
- 4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 31
Description
e.g., we could have mcp_python as just the base definitions, mcp_python[stdio], mcp_python[sse], etc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the package metadata and the declarations for stdio and SSE transport dependencies, then compare the current installation behavior with the proposed base package and transport-specific extras. Done means the package can be installed with each requested transport extra while keeping the base installation minimal, with coverage for the supported extras.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100