Why It MattersUsers and operators can now manage MCPs directly in the web interface (browse catalog, attach/detach, and toggle local/global scope) instead of falling back to terminal-only workflows, which makes session MCP setup and maintenance faster and operationally consistent; this also enables automated MCP operations through a defined API contract. The web and TUI now share the same session persistence path, reducing risk of divergent `.mcp.json` behavior, but parity should be watched around scope validation, mutation-disabled paths, and remote-session path handling as MCP coverage grows.
ImpactUsers and operators can now manage MCPs directly in the web interface (browse catalog, attach/detach, and toggle local/global scope) instead of falling back to terminal-only workflows, which makes session MCP setup and maintenance faster and operationally consistent; this also enables automated MCP operations through a defined API contract. The web and TUI now share the same session persistence path, reducing risk of divergent `.mcp.json` behavior, but parity should be watched around scope validation, mutation-disabled paths, and remote-session path handling as MCP coverage grows.