Describe the bug
Running openbb-mcp-server via uvx fails immediately after startup with an uninformative error — the actual exception message is not printed, only a bare "Server error:" label.
To Reproduce
uvx --from openbb-mcp-server --with openbb openbb-mcp --transport stdio
- Server logs "Loaded bundled skills..." and "Added default system prompt with skill awareness nudge."
- Immediately after, logs
ERROR Server error: (app.py:1027) with no exception detail, and the process exits.
Environment
- OS: Windows
- Installed via:
uvx (using uv)
- No
~/.openbb directory exists (fresh user, never configured)
- No
~/.openbb_platform/mcp_settings.json exists
What I've ruled out
- PATH issues —
uvx.exe resolves correctly, confirmed via logs and manual terminal run
- Windows console encoding — set
chcp 65001, PYTHONUTF8=1, PYTHONIOENCODING=utf-8; identical crash
- Corrupted/stale cached packages — ran
uv cache clean (removed 23,391 files), reinstalled all 149 packages fresh in 3.92s; identical crash
- Corrupted local OpenBB config — no
.openbb directory exists to be corrupted
- Reproducible identically both via
uvx directly in a terminal and via Claude Desktop's MCP server launcher
Expected behavior
Either the server starts successfully, or — at minimum — the actual exception (type + message + traceback) should be logged instead of a bare "Server error:" with no detail. The current logging swallows the real cause, making this impossible to self-diagnose.
Additional context
Ran openbb-mcp --help — no --verbose or --log-level flag is exposed that would help surface the underlying exception.
Describe the bug
Running
openbb-mcp-serverviauvxfails immediately after startup with an uninformative error — the actual exception message is not printed, only a bare "Server error:" label.To Reproduce
uvx --from openbb-mcp-server --with openbb openbb-mcp --transport stdioERROR Server error:(app.py:1027) with no exception detail, and the process exits.Environment
uvx(usinguv)~/.openbbdirectory exists (fresh user, never configured)~/.openbb_platform/mcp_settings.jsonexistsWhat I've ruled out
uvx.exeresolves correctly, confirmed via logs and manual terminal runchcp 65001,PYTHONUTF8=1,PYTHONIOENCODING=utf-8; identical crashuv cache clean(removed 23,391 files), reinstalled all 149 packages fresh in 3.92s; identical crash.openbbdirectory exists to be corrupteduvxdirectly in a terminal and via Claude Desktop's MCP server launcherExpected behavior
Either the server starts successfully, or — at minimum — the actual exception (type + message + traceback) should be logged instead of a bare "Server error:" with no detail. The current logging swallows the real cause, making this impossible to self-diagnose.
Additional context
Ran
openbb-mcp --help— no--verboseor--log-levelflag is exposed that would help surface the underlying exception.