Cline: Invalid MCP settings format

What it means

Cline could not validate cline_mcp_settings.json against its MCP settings schema, so no servers load.

Causes

• Settings file that does not match the expected schema (for example a missing top-level "mcpServers" object).
• Reported on 3.8.3 and 3.16.3 even after marketplace installs; consolidated by maintainers into the MCP system issues tracker #4391.

How to fix it

1. 1
   Fix 1.

   Use the documented structure: a top-level "mcpServers" object, one entry per server. Local (STDIO) example from the docs:

   JSON

   Copy

   {
     "mcpServers": {
       "local-server": {
         "command": "node",
         "args": ["/path/to/server.js"],
         "env": {
           "API_KEY": "your_api_key"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }

2. 2
   Fix 2.

   For remote servers, the docs say the "type" field selects the transport; omitting it defaults to legacy "sse", so set "type": "streamableHttp" explicitly.

   JSON

   Copy

   "type": "streamableHttp"

3. 3
   Fix 3.

   Update Cline: 4.0.0 "Migrate legacy MCP files and formats into the shared settings file and protect MCP settings writes with safer locking/atomic updates."