Linter issues in MCP server

[bartmichalak]

When I created new MCP server based on the boilerplate and push the code, linter returned some issues:
https://github.com/bartmichalak/mcp-server-python-sample/actions/runs/18190098723

Then I ran:
uv run ruff check . --fix

However it didn't fix one of them:
https://github.com/bartmichalak/mcp-server-python-sample/actions/runs/18192151773

Proposed Solution

• Predefined hooks for pre-commit?

[Sam-Radnus]

@bartmichalak can I work on this issue

[KaliszS]

@Sam-Radnus Hi!

Of course you can start a Pull Request :) But may I ask what is your idea for that? Because I see two potential solutions and none of them seems to be a working solution:

• we can add copier task to run pre-commit after generating project, but it's going to end up with manual errors that users will be supposed to fix on their own and I don't think that's what we want to achieve
• we can sort this on the template side, but it's not so easy because of the jinja template files -> they contain a lot of if-elif-else flows and I see two separate issues here:
  • we can't really maintain imports orders (this is isort reponsibility), because some of the if statements contain shared imports (shared between different project types)
  • pre-commit hooks (like ruff or ty) can't handle python code within jinja syntax, but maybe you know hooks that can solve that?