Manage client configurations

MCP Dock can target common desktop and CLI clients, including Cursor, VS Code, Claude Code, Gemini CLI, Codex CLI, Windsurf, Zed, TRAE, Kiro, and JetBrains tools. Choose only the clients where the server is needed. A server configured for one client is not automatically appropriate for another client with a different trust boundary or workflow.

Before writing a configuration, note the server command, arguments, working directory, declared transport, and environment variables. After installation, open the client’s configuration and compare it with the intended values. Keep secrets in the client or operating-system mechanism you normally use; do not paste credentials into screenshots, issue reports, or public configuration examples.

Disable the most recently added server first, then inspect the client’s own logs. Invalid JSON, unavailable runtimes, duplicate server names, and missing environment variables are common causes. Restore a known-good configuration before trying a different server or editing unrelated client settings.