[BUG] Custom MCP server is overwritten after login

[onelxj]

Issue

I start my McpJam app with npx @mcpjam/inspector@latest --config mcp_servers.json --server ai-todo

the config looks like the following:
{"mcpServers":{"ai-todo":{"type":"streamable-http","url":"http://localhost:9991/mcp/"}}}

then it opens a window which indeed connects to my server:

but later to use the chat I have to sign in, my server is not shown anymore and I have to manually add it:

Expected Behavior

The connected server from my config will be autoconnected after the login and shown in the list of servers.

Platform

• npx

[dosubot]

Hi @onelxj! I'm Dosu and I’m helping the inspector team.

This appears to be related to several known configuration persistence issues in the Inspector:

Related bugs:

• Issue #904: Authentication Configuration is not saved properly - config resets on reload
• Issue #988: Reconnecting HTTP Servers causes OAuth to be re-enabled - lingering OAuth data causes issues
• Issue #118: --config flag doesn't work - basic --config functionality issues

Some of these have been fixed (Issue #904 in commit 68b7543, Issue #118 in PR #186), but your specific scenario of servers disappearing after sign-in may be a variation that hasn't been fully addressed.

Workaround: Try clearing localStorage for the Inspector. Specifically look for keys like mcp-oauth-config-ai-todo and other OAuth-related entries that may be overriding your CLI-provided configuration.

The root cause likely involves how localStorage OAuth data takes precedence over CLI config during authentication state changes, or a potential race condition between workspace syncing and config loading during login.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}