- 
                Notifications
    You must be signed in to change notification settings 
- Fork 2.7k
Description
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 (
| log_level: Literal["DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"] = "INFO" | 
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 (), which should be prevented.python-sdk/src/mcp/server/fastmcp/server.py Line 138 in c2ca8e0 configure_logging(self.settings.log_level) 
- The configuration of uvicorn () that if the parameters log_config and log_level are not None also makes the change.python-sdk/src/mcp/server/fastmcp/server.py Line 471 in c2ca8e0 config = uvicorn.Config(