Skip to content
Conduit

Config Editor & Profiles

Config Editor

Section titled “Config Editor”

The Servers tab shows all detected MCP clients and their configuration files. Click on a client to open the Config Editor — a full Monaco editor for the client’s JSON config.

Features

Section titled “Features”
  • Syntax highlighting and auto-formatting
  • Live validation — the editor checks your config structure as you type and shows issues in the panel below
  • Dirty state tracking — unsaved changes are indicated visually
  • Backup on save — every save creates a timestamped backup at ~/.conduit/backups/

Validation

Section titled “Validation”

The validator checks for:

  • Valid JSON syntax
  • Required mcpServers top-level key
  • Correct structure for each server entry (command, args, env)
  • Nested projects.*.mcpServers layout (used by Claude Code)

Issues are shown with severity levels and line numbers in the panel below the editor.

Profiles

Section titled “Profiles”

Profiles let you save and switch between different sets of MCP server configurations — useful when you work on different projects or want to toggle between development and production servers.

Creating a Profile

Section titled “Creating a Profile”
  1. Open the Servers tab
  2. Click the Profile dropdown in the header
  3. Choose Save as Profile
  4. Name your profile (e.g. “Work”, “Personal”, “Project X”)

The current configuration of all detected clients is saved as a snapshot.

Applying a Profile

Section titled “Applying a Profile”
  1. Open the Profile dropdown
  2. Select the profile you want to apply
  3. Conduit writes the saved configs back to each client’s config file
  4. Restart your AI clients to pick up the changes

Managing Profiles

Section titled “Managing Profiles”

From the Profile dropdown you can:

  • Rename — change the display name
  • Delete — remove the profile (does not affect current configs)
  • Overwrite — save the current state over an existing profile