Option to not rewrite the logging configuration

Is your feature request related to a problem? Please describe.
We are integrating FastMcp into a larger python process that requires a custom logging handler and when initialising the FastMCP server (in our case in sse mode) we see that the logging library configuration changes with a custom configuration of the server itself.

Describe the solution you'd like
Define a configuration parameter that disables the logging configuration performed by the server.

Describe alternatives you've considered
Reviewing the configuration parameters I have seen the existence of the parameter log_level (https://github.com/modelcontextprotocol/python-sdk/blob/c2ca8e03e046908935d089a2ceed4e80b0c29a24/src/mcp/server/fastmcp/server.py#L71) and perhaps if this parameter allowed the value None this could prevent the reconfiguration from being carried out.

Additional context
As far as I have been able to identify, there are two points where this configuration is being made and which should be modified:

• The call to the configure_logging method (https://github.com/modelcontextprotocol/python-sdk/blob/c2ca8e03e046908935d089a2ceed4e80b0c29a24/src/mcp/server/fastmcp/server.py#L138), which should be prevented.
• The configuration of uvicorn (https://github.com/modelcontextprotocol/python-sdk/blob/c2ca8e03e046908935d089a2ceed4e80b0c29a24/src/mcp/server/fastmcp/server.py#L471) that if the parameters log_config and log_level are not None also makes the change.

Commencez dans src/mcp/server/fastmcp/server.py, au niveau de l’appel à configure_logging vers la ligne 138, ainsi que de la configuration de uvicorn vers la ligne 471. Suivez la façon dont log_level et log_config sont transmis en mode SSE, puis définissez et vérifiez l’option qui laisse inchangée la configuration de logging de l’application hôte.