MCP toggle

Turns Claude's and Codex's MCP servers on or off per project. Claude's switches use the per-project list Claude's own /mcp command uses (disabledMcpServers in ~/.claude.json). Codex starts each project with ~/.codex/config.toml's state; a switch writes enabled for that server into the project's own .codex/config.toml, and switching back to the default removes it again.

• Before a session: open Manage MCP servers at the top of the sidebar and pick a project. Its Claude and Codex servers sit side by side; flip them there. New sessions start with that set.
• During a chat: the mcp servers pill above a Claude or Codex agent's composer lists that provider's servers and whether each is enabled. Picking one toggles it and reloads the agent's session so the change takes effect. If the agent was working, the reload stops its turn and the plugin asks it to continue.

A subfolder or a worktree uses its main repository's settings. For Codex, which only reads a worktree's own .codex/config.toml, a switch lands in the main checkout and every worktree, and a worktree made later gets the project's switches before Codex opens in it. A .codex/config.toml the plugin creates is added to the repository's .git/info/exclude so agents do not commit it. Codex reads project settings only in projects it trusts, and never in your home folder, so those show as locked. Each Codex edit is read back through codex app-server and undone if Codex disagrees.

ZeroSub account homes get the same Claude change. Reloading uses the paseo command-line tool on the daemon's machine, and Codex needs the codex command-line tool there. Servers from Claude's .mcp.json files or from Claude and Codex plugins are not covered.