modelcontextprotocol / modelcontextprotocol/python-sdk
Audit MCPServer constructor parameters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.3k
- Forks
- 4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 31
Description
From the V2 checklist in #1253:
We need to recheck the constructor parameters of the MCPServer class. I did remove and refactor a bit, but we need to audit it a bit better.
PR #1732 renamed FastMCP to MCPServer and moved transport-specific options (host, port, stateless_http, etc.) to run(). However, the constructor still has parameters that may need further review:
- Are all remaining constructor parameters appropriate for the constructor vs.
run()? - Are there parameters that should be removed, renamed, or have their defaults reconsidered?
- Is the constructor signature clean and minimal for the common case?
This is a follow-up audit to ensure the MCPServer API surface is well-designed before V2 stabilizes.
Ref: Kludex's V2 checklist in #1253, follow-up to #1732
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
Start by reviewing the MCPServer constructor and its run() entry point, along with the changes from PR #1732 and the V2 checklist in #1253. Audit which parameters belong in each API and document or test the resulting decisions so the constructor is minimal and suitable for V2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100