fix(cli): handle malformed MCP config files in remove detection (#2574)

readJsonConfig only caught file-read errors, not JSON.parse errors.
During `ctx7 remove`, the detector iterates every agent's well-known
config path; an unparseable JSON file at any of them (e.g. a
hand-edited ~/.claude.json) crashed the command with an unhandled
SyntaxError before it could do anything.

Wrap the readJsonConfig call in hasMcpConfig with a try/catch that
logs a warning naming the path and parse error and skips that agent.
Keep readJsonConfig itself strict so write paths in setup and
uninstallMcp continue to surface failures via their existing handling.

Author: fahreddinozcan

.changeset/handle-mcp-config-detection-errors.md

@@ -0,0 +1,5 @@
+---
+"ctx7": patch
+---
+
+Handle malformed MCP config files gracefully during `ctx7 remove` agent detection. Previously, an unparseable JSON config at any agent's well-known path (e.g. a hand-edited `~/.claude.json`) would crash the command with an unhandled `SyntaxError` before it could do anything. The detector now skips the offending file and logs a warning naming the path and parse error so the user can fix it, while detection continues for the remaining agents.

packages/cli/src/commands/remove.ts

@@ -198,7 +198,15 @@ async function hasMcpConfig(agentName: SetupAgent, scope: Scope): Promise<boolea
     return readTomlServerExists(mcpPath, "context7");
   }
 
-  const existing = await readJsonConfig(mcpPath);
+  let existing: Record<string, unknown>;
+  try {
+    existing = await readJsonConfig(mcpPath);
+  } catch (err) {
+    log.warn(
+      `Skipped ${mcpPath}: could not parse (${err instanceof Error ? err.message : String(err)})`
+    );
+    return false;
+  }
   const section = existing[agent.mcp.configKey];
   return (
     !!section && typeof section === "object" && !Array.isArray(section) && "context7" in section