Your MCP server is configured once per AI app.
Claude Desktop, Cursor, Windsurf, VS Code, Codex, and Kiro use different files and native shapes. Manual copying creates drift, stale values, malformed configuration, and edits that are hard to review or undo.
A deliberately bounded workflow
- 1 Define once Import compatible local definitions or add a complete local STDIO server to canonical versioned configuration.
- 2 Preview the exact plan Validate and render every supported target in memory before the first write, with sensitive values structurally redacted.
- 3 Apply recoverably Preserve client-owned fields, skip no-ops, retain adjacent backups, and roll back earlier writes when a later target fails.
Configuration only—until you explicitly test.
Know what the utility will—and will not—do
init, list, sync, and restore do not start MCP servers. Only test executes one named local definition. Project-level files, remote entries, credential stores, and unowned client settings stay outside the managed boundary.