[feature] MCP servers: add, edit, copy and remove from the panel

[YJack0000]

Stacked on #12 — retarget to main once that merges.

The matrix could already show you that Cursor was missing a server Claude Code has, then leave you to go fix it in a JSON file. Now a row opens a drawer.

Flows

• Edit — click a row: chips for every client holding that server, form prefilled from read_spec for the one you picked (transport, command/args or url, env, headers). Explicit save; nothing autosaves; a dirty drawer asks before closing.
• Switch client copy — the form always shows exactly one client's copy and says whose. Six clients keep six files and Cursor's definition can differ from Codex's, so a save writes one file rather than flattening the difference.
• Copy — every client missing the server gets a "copy here"; the report names which env/header values travelled.
• Remove — inline confirm row (the vault's idiom), not a dialog. A project: scoped Claude Code entry is shown and explained rather than offered, so core's claude mcp remove message surfaces where you'd try.
• Add — + add server opens the same drawer empty with a checkbox per client; absent config files say "will be created".

Value boundary unchanged. mcp_list (fills the table, refreshes after every write) still reports env/header names and an argument count only. Values cross exactly one new command, for one named server of one named client, because you opened its drawer.

Every write reuses the core path the CLI already uses: rolling backup, parse–modify–serialize, atomic rename, JSON style and TOML comments preserved. The report names the file written, the backup, and repeats core's notes including the restart caveat.

Four new Tauri commands (mcp_read_spec/mcp_add/mcp_remove/mcp_copy) + serde wire mirrors with two unit tests guarding the #[serde(flatten)] shape every save is built from. Args are one input per argument — any single-field encoding can mangle an existing arg on an edit round-trip. Headers show for stdio too, because core writes and reads them regardless and hiding the section would silently drop data.

clippy -D warnings + cargo build --locked + bun run build clean; no workspace crate or lockfile touched.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud