MCP server config using npx from smithery Initialization failed Connection timeout after 30000ms #8731
-
What happened?tried to use smithery and config MCP servers manually in librechat.yaml such as context7 and yahoo finance however, both have the same issues where MCP server failed to initialize, am I missing anything? I am deploying librechat via k8s using deployment object where pod are all ephemeral, so I am not running npx command manually and restarting the server, but instead config it in librechat.yaml Version Informationv0.7.9-rc1 Steps to Reproduceadd either of following block in librechat.yaml mcpServers: What browsers are you seeing the problem on?Chrome Relevant log output2025-07-29T16:07:17.446Z info: Initializing MCP servers...
2025-07-29T16:07:17.696Z debug: [mcp_get_tokens:tokens:000000000000000000000000:yahoo-finance] Creating initial flow state
2025-07-29T16:07:17.699Z info: [MCP][yahoo-finance] Access token missing
2025-07-29T16:07:17.700Z info: [MCP][yahoo-finance] Access token missing and no refresh token available
2025-07-29T16:07:17.713Z info: [MCP][yahoo-finance] Setting up OAuth event listener
2025-07-29T16:07:17.733Z debug: [MCP][yahoo-finance] Transport sending: {"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"@libre... [truncated]
npm warn deprecated [email protected]: Use your platform's native DOMException instead
- Resolving @hwangwoohyun-nav/yahoo-finance-mcp...
✔ Successfully resolved @hwangwoohyun-nav/yahoo-finance-mcp
2025-07-29T16:07:47.714Z error: [MCP][yahoo-finance] Initialization failed Connection timeout after 30000ms
2025-07-29T16:07:47.715Z info: [MCP] Initialized 0/1 app-level server(s)
2025-07-29T16:07:47.715Z warn: [MCP] 1/1 app-level server(s) failed to initialize
2025-07-29T16:07:47.715Z info: [MCP][yahoo-finance] ✗ Failed
2025-07-29T16:07:47.715Z warn: [MCP] No app-level servers initialized
2025-07-29T16:07:47.716Z info: MCP servers initialized successfullyScreenshotsNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 42 replies
-
|
I believe your error is stemming from attempting to construct the MCP server definition in
You should execute that command in your terminal (same goes for yahoo-finance), and it will auto construct the proper definition for you and inject it into the YAML file. Let me know if this resolves your issue or if we need to troubleshoot further. |
Beta Was this translation helpful? Give feedback.
-
|
hmm.. I think I might remembered things wrong, if I click the 
I used to remember clicking an offline MPC server on the text portion it used to pop up a UI asking me to input credentials, I might have clicked wrong places, nvm then, everything seems correct now, appreciate your time and patience |
Beta Was this translation helpful? Give feedback.
-
|
Glad we got things resolved for you! I will look into your mongodb issue with the anomalous record as well later tonight and see if I can replicate. |
Beta Was this translation helpful? Give feedback.
-
|
Quick update: your Set/Unset state behavior helped point out an inconsistency in the way we were fetching authFields, so thank you for raising that. A PR has been opened and merged addressing the issue: #8905 |
Beta Was this translation helpful? Give feedback.
-
|
nice! I did observe that but unsure if that'a bug or not, appreciate your quick fixes |
Beta Was this translation helpful? Give feedback.
-
|
smithery-ai/cli#331 has been merged! |
Beta Was this translation helpful? Give feedback.
I believe your error is stemming from attempting to construct the MCP server definition in
librechat.yamlusing the autogenerated installation command from Smithery, rather than allowing the command to construct the definition for you.npx -y @smithery/cli@latest install @upstash/context7-mcp --client librechat --profile xxxxx-xxxxx-xxxxx --key xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxYou should execute that command in your terminal (same goes for yahoo-finance), and it will auto construct the proper definition for you and inject it into the YAML file.
Let me know if this resolves your issue or if we need to troubleshoot further.