refactor: move transport-specific parameters from FastMCP constructor to run() #1898
+339
−231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
host,port,json_response,stateless_http,event_store,retry_interval,sse_path,message_path,streamable_http_path,transport_security) from theFastMCPconstructor torun(),sse_app(), andstreamable_http_app()@overloaddecorators torun()for proper type hints per transport typeThis improves the API by separating server configuration from transport configuration. Transport parameters are now only relevant where they're used.
BREAKING CHANGE: Transport-specific parameters must now be passed to
run()or the transport app methods instead of theFastMCPconstructor.Test plan
🤖 Generated with Claude Code