FastMCP 2.0 Migration & Foundation #19
Merged
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
This PR migrates the KiCad MCP server to FastMCP 2.0 and establishes a solid foundation for the project. This is the first of several PRs that will modernize the codebase and add comprehensive functionality.
Key Changes
mcp.server.fastmcpto modernfastmcppyproject.tomlwith hatchling build backendTechnical Details
kicad_mcp/server.pyto use FastMCP 2.0 importsmain()function with proper async server lifecyclepyproject.tomlfor modern Python packaging standardsmain.pyto use new async entry pointTesting
Dependencies
This PR establishes the foundation for subsequent PRs:
Review Notes
This is a minimal, focused change that ensures the server runs on FastMCP 2.0. All existing functionality is preserved while establishing the foundation for future improvements.