mcp-config-editor

MCP Config Editor is a desktop tool for creating and editing MCP server configuration files used by clients like Claude Desktop. It provides a user-friendly interface to paste in an existing server Readme JSON, modify fields (such as server name, host, port, authentication, or any custom MCP settings), and save or export the updated configuration. This makes it easy to assemble or adjust the MCP server definitions you’ll feed into your MCP-enabled apps without manually editing JSON in a text editor. Use the editor to import a server configuration, tweak the fields you need, and then export the resulting MCP configuration file for use with Claude Desktop or other MCP-compatible clients.

What you can do with this app includes: pasting JSON from a server Readme to populate a configuration, editing specific fields in each server entry, saving your changes locally, and exporting configuration files to share or reuse. You can also add server details manually if you don’t have a JSON draft handy, ensuring you have a valid MCP configuration structure for your deployments.

Prerequisites:

• A computer with a modern operating system (Windows, macOS, or Linux)
• Node.js (recommended LTS) and npm installed
• Git installed

Install and run locally:

1. Clone the repository: git clone https://github.com/yourusername/mcp-config-editor.git
2. Navigate to the project directory: cd mcp-config-editor
3. Install dependencies: npm install
4. Run the app in development mode: npm run dev

Optional: build for production (Electron):

• Ensure you have the necessary build tooling installed according to the project’s package.json scripts.
• Run the build script, for example: npm run build

Notes:

• The app is distributed as a desktop Electron application. On Windows you’ll typically download an installer from the Releases page, while macOS and Linux builds are available as installers or AppImages, depending on the project’s release assets.

Tips and common issues:

• This editor focuses on MCP server configuration structure. Ensure your JSON conforms to the MCP Readme schema used by Claude Desktop and other MCP clients.
• If you encounter JSON validation errors, verify required fields such as server name, host, and port are present and correctly typed.
• When exporting, use a filename that clearly indicates it contains MCP server configurations to avoid confusion with other JSON files.
• If you’re integrating with Claude Desktop, you may want to maintain separate configuration exports per environment (e.g., development, staging, production).
• The MCP configuration format in this tool is designed to be consumed by MCP clients directly; validate with your target client after export to ensure compatibility.