Feature
When launching the inspector with npx @mcpjam/inspector --config mcp_servers.json --server <name>, the server is loaded into the current anonymous session. As soon as I sign in, the UI switches to my account's workspace and the CLI-loaded server disappears — I have to re-add it manually through the sidebar.
This forces a choice between two workflows that should work together:
CLI-driven loading (--config) is the fastest way to spin up the inspector against a specific server during local dev.
Chat is so useful during development.
Right now you can only have one or the other in a single session.
Solution
When the local session is started and connected to the local MCP server it shouldn't be lost after the sign in.
Feature
When launching the inspector with
npx @mcpjam/inspector --config mcp_servers.json --server <name>, the server is loaded into the current anonymous session. As soon as I sign in, the UI switches to my account's workspace and the CLI-loaded server disappears — I have to re-add it manually through the sidebar.This forces a choice between two workflows that should work together:
CLI-driven loading (
--config) is the fastest way to spin up the inspector against a specific server during local dev.Chat is so useful during development.
Right now you can only have one or the other in a single session.
Solution
When the local session is started and connected to the local MCP server it shouldn't be lost after the sign in.