Toolport writes MCP config for ~22 AI clients via the defs() table in src-tauri/src/clients.rs. Witsy is an MCP client that is not supported yet, and adding it is a clean, self-contained first PR.
Add a ClientDef for it: the per-OS config path, the format variant (JsonMcpServers / JsonServers / TomlMcpServers), and connector-vs-file, plus a fixture test alongside the existing client_config_path tests (around clients.rs:3569). Copy an existing entry such as boltai or continue as a template. Most desktop clients use the JsonMcpServers shape (a top-level mcpServers object); confirm Witsy's actual config path and shape per OS before wiring it.
See CONTRIBUTING.md and the umbrella issue #271 for the pattern. Comment here to claim it.
Acceptance: Witsy appears in the Clients view and its config round-trips through a fixture test.
Toolport writes MCP config for ~22 AI clients via the
defs()table insrc-tauri/src/clients.rs. Witsy is an MCP client that is not supported yet, and adding it is a clean, self-contained first PR.Add a
ClientDeffor it: the per-OS config path, the format variant (JsonMcpServers/JsonServers/TomlMcpServers), and connector-vs-file, plus a fixture test alongside the existingclient_config_pathtests (aroundclients.rs:3569). Copy an existing entry such asboltaiorcontinueas a template. Most desktop clients use theJsonMcpServersshape (a top-levelmcpServersobject); confirm Witsy's actual config path and shape per OS before wiring it.See CONTRIBUTING.md and the umbrella issue #271 for the pattern. Comment here to claim it.
Acceptance: Witsy appears in the Clients view and its config round-trips through a fixture test.