Use Claude CLI tools for MCP configuration instead of writing JSON manually

[pento]

Problem

The setup wizard currently writes MCP server configuration directly to the Claude Code JSON config files. The Claude CLI now has built-in commands for managing MCP servers (e.g., claude mcp add, claude mcp get, claude mcp list, claude mcp remove) which handle config file management, scope resolution, and validation.

Proposed solution

Switch the setup and configuration code to use the Claude CLI MCP commands instead of manually reading/writing JSON config files. Benefits:

• Simpler code: no need to manage config file paths, JSON parsing, or scope logic ourselves.
• Cross-context visibility: can detect MCP servers installed in other scopes (global, project, etc.) via claude mcp list / claude mcp get.
• Forward compatibility: CLI commands will handle any future config format changes.

For example, claude mcp get wpce already shows scope and connection status, which could replace some of our manual detection logic.