MCP Config Editor is a lightweight GUI tool built to help you manage multiple MCP (Minecraft Command Protocol) servers without manually editing configuration files. The app provides a simple dashboard where you can toggle MCP servers on or off, view their status, and apply configuration changes across your managed MCP instances. Being built with tauri2, it runs as a native desktop application, offering a responsive UI and integrates with your local environment to execute MCP-related commands as configured in the mcpServers section. Use it to quickly enable or disable servers, and keep track of which MCP instances are currently active.

Prerequisites:

• A supported OS (macOS, Linux, or Windows) with a practical environment for building or running a tauri-based app.
• Node.js and a package manager (npm or pnpm) if you plan to build from source.
• Rust toolchain (Rustup) and cargo if you intend to build the tauri app from source.

Install from source (typical workflow):

1. Clone the repository: git clone <repository-url> cd mcp-config-editor

2. Install dependencies (if applicable): npm install

   or, if using pnpm

   pnpm install

3. Build the project (tauri-based): npm run build

   or the equivalent cargo/tauri build command as defined in the project

4. Run the app locally for development: npm run dev

If you prefer a binary, download the prebuilt release from the project’s releases page and run the executable for your OS.

Notes:

• This GUI is designed to help you manage MCP servers but does not replace traditional MCP server configuration. Ensure your underlying MCP setup is correctly configured and reachable by the editor.
• Because this is built with tauri, you may encounter platform-specific permissions prompts. Grant the necessary permissions to allow the app to execute external MCP commands.
• If you add or modify servers, update the mcpServers configuration in the mcp_config to reflect the correct command, arguments, and any required environment variables.
• Common issues include incorrect path to server scripts, missing dependencies for the MCP runtime, or firewall rules blocking local communication. Check logs within the app for error messages and verify your environment variables.
• Environment variables (env) can be used to point to configuration files, define MCP runtime paths, or set API keys if you integrate with external tools.
• This README references a minimal example; adapt the mcp_config to your actual MCP deployment paths and runtime commands.