conductorv2

Integrations · AI Clients

Continue.dev

Continue uses an array for mcpServers, not an object. This is the most common mistake when copying configs from other clients.

Config file location

PlatformPath
macOS / Linux~/.continue/config.json
Windows%USERPROFILE%\.continue\config.json

You can also open it from VS Code: Continue sidebar → gear icon → Open config.json.

Setup

Important: array syntax

Unlike Claude Desktop or Cursor, Continue uses an array [] for mcpServers, not an object {}. Each server entry also uses name instead of being keyed by name.

~/.continue/config.json
// ~/.continue/config.json
// Note: mcpServers is an ARRAY in Continue, not an object
{
  "mcpServers": [
    {
      "name": "conductor",
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"]
    }
  ]
}
with plugin credentials
{
  "mcpServers": [
    {
      "name": "conductor",
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token",
        "CONDUCTOR_LOG_LEVEL": "info"
      }
    }
  ]
}

After saving

1Save config.json.
2Continue auto-reloads the config. If tools don't appear, run the Reload Window command (⌘⇧P → Developer: Reload Window).
3In the Continue chat panel, type: 'list the files in this directory' — you should see filesystem.list called.

Troubleshooting

"mcpServers must be an array"

You used object syntax {} instead of array syntax []. Wrap the server entry in square brackets as shown above.

MCP not loading after config save

Try: VS Code Command Palette → Continue: Open Logs — look for MCP startup errors. Then try Reload Window.

Tools visible in settings but not used

Continue's MCP tool use depends on the model's capabilities. Use a model with tool-calling support (Claude, GPT-4o). Older models may not trigger MCP.

npx PATH issues in VS Code

Use the full absolute path to npx. Run which npx in a terminal to find it, then use that path as the command value.

WindsurfAider