GitHub issue #10894 in cline/cline, opened 2026-05-19 by DavidHinton-xcpc, records a report that when using VS Code Portable Mode, the MCP server configuration written into settings.json via cline.mcpServers is completely ignored by Cline, that Cline does not read MCP settings from settings.json at all and only reads from a standalone cline_mcp_settings.json file, and that MCP servers defined in settings.json do not appear in Cline's Connected MCP Servers list; the author also reports that in portable mode VS Code stores settings under the portable data directory rather than the standard path, and that the cline_mcp_settings.json file was auto-created at some point. System cited: VS Code 1.120.0 Portable Mode, Cline 3.83.0, Windows 10.
Verbatim Excerpts from Cited Records
“When using VS Code **Portable Mode**, the MCP server configuration written into `settings.json` via `cline.mcpServers` is **completely ignored** by Cline.”
“Additionally, Cline does not read MCP settings from `settings.json` at all — it only reads from a standalone `cline_mcp_settings.json` file.”
“MCP servers do **not** appear.”
·
cline/cline (issue 10894 opening body, Actual Behavior section)
·
2026-05-19T14:07:46Z
·GitHub Issue ↗
“The `cline_mcp_settings.json` file was auto-created at some point, suggesting Cline itself recognizes this file as the MCP config source.”
·
cline/cline (issue 10894 opening body, Additional Notes section)
·
2026-05-19T14:07:46Z
·GitHub Issue ↗
Counter-record: Issue closed 2026-11-14 by linear-code[bot] with state_reason not_planned and a stale label; no closing comment appears in the thread and no fix was confirmed there, so the close reads as a stale cleanup, not a fix and not a retraction of the report. All 3 comments read. linear-code[bot] (2026-05-19) linked the report to CLINE-2238. github-actions[bot] (2026-07-20) marked the issue stale after 60 days without activity. jfkguidant (2026-08-13) added a related portable-mode report: Cline installed in portable VS Code on Windows 11 uses home/.cline/data/globalState.json, which prevents running multiple instances with different settings, and asked whether globalState.json can be redirected into the portable data directory. No maintainer response, no fix, and no retraction appear in the thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #10894 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.