modelcontextprotocol
Add support for Inspector configuration settings in CLI mode
Is your feature request related to a problem? Please describe
When using the Inspector in CLI mode, there's currently no way to configure Inspector-specific settings like MCP_SERVER_REQUEST_TIMEOUT. This limitation forces users to work with default timeout values, which may not be suitable for all use cases, especially when dealing with slower MCP servers or long-running operations.
Describe the solution you'd like
Add support for passing Inspector configuration settings in CLI mode, similar to how they can be configured in the UI.
This would allow users to customize timeout values, proxy addresses, and other Inspector settings when running in CLI mode.
Describe alternatives you've considered
- Setting environment variables for these configurations (e.g.,
MCP_SERVER_REQUEST_TIMEOUT=15000) - Creating a global configuration file that applies to both UI and CLI modes
- Modifying source code directly for custom timeout values (not user-friendly)
Additional context
Current Inspector configurations like MCP_SERVER_REQUEST_TIMEOUT, MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS, and others defined in configurationTypes.ts should be made accessible in CLI mode. This would provide a consistent configuration experience across both UI and CLI modes and improve usability for automation and scripting scenarios.
Went through the PR #271 and got idea about the implementation of configuration in client also explored on implementation for cli mode. Just want to check with you guys if this FR is valid to work on ? @olaservo @cliffhall @pulkitsharma07
Hi @Kavyapriya-1804 thanks for checking and for offering to work on this - yes, I think it would make sense to support the same optional settings in CLI mode, especially for timeout settings.
Hi @olaservo, @cliffhall, @pulkitsharma07, @HaiyiMei I have added support for the 3 request configurations, added the observations and would like to have your suggestions for the items discussed in #373 !